Download the PHP package spatie/laravel-personal-data-export without Composer

On this page you can find all versions of the php package spatie/laravel-personal-data-export. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package laravel-personal-data-export

Create zip files containing personal data

Latest Version on Packagist run-tests Check & fix styling Total Downloads

This package makes it easy to let a user download an export containing all the personal data. Such an export consists of a zip file containing all the user properties and related info.

You can create and mail such a zip by dispatching the CreatePersonalDataExportJob job:

The package will create a zip containing all the personal data. When the zip has been created, a link to it will be mailed to the user. By default, the zips are saved in a non-public location, and the user should be logged in to be able to download the zip.

You can configure which data will be exported in the selectPersonalData method on the user.

You can store files in a directory of the archive. For this, add the directory path as the third parameter.

This package also offers an artisan command to remove old zip files.

Support us

We invest a lot of resources into creating best in class open source packages. You can support us by buying one of our paid products.

We highly appreciate you sending us a postcard from your hometown, mentioning which of our package(s) you are using. You'll find our address on our contact page. We publish all received postcards on our virtual postcard wall.

Installation

You can install the package via composer:

You need to use this macro in your routes file. It'll register a route where users can download their personal data exports.

You must add a disk named personal-data-exports to config/filesystems (the name of the disk can be configured in config/personal-data-export). You can use any driver that you want. We recommend that your disk is not publicly accessible. If you're using the local driver, make sure you use a path that is not inside the public path of your app.

To automatically clean up older personal data exports, you can schedule this command in your console kernel:

Optionally, you can publish the config file with:

This is the content of the config file, which will be published at config/personal-data-export.php:

Usage

Selecting personal data

First, you'll have to prepare your user model. You should let your model implement the Spatie\PersonalDataExport\ExportsPersonalData interface. This is what that interface looks like:

The selectPersonalData is used to determine the content of the personal download. Here's an example implementation:

$personalData is used to determine the content of the zip file that the user will be able to download. You can call these methods on it:

The name of the export itself can be set using the personalDataExportName on the user. This will only affect the name of the download that will be sent as a response to the user, not the name of the zip stored on disk.

Creating an export

You can create a personal data export by executing this job somewhere in your application:

By default, this job is queued. It will copy all files and content you selected in the selectPersonalData on your user to a temporary directory. Next, that temporary directory will be zipped and copied over to the personal-data-exports disk. A link to this zip will be mailed to the user.

Securing the export

We recommend that the personal-data-exports disk is not publicly accessible. If you're using the local driver for this disk, make sure you use a path that is not inside the public path of your app.

When the user clicks the download link in the mail that gets sent after creating the export, a request will be sent to underlying PersonalDataExportController. This controller will check if there is a user logged in and if the request personal data zip belongs to the user. If this is the case, that controller will stream the zip to the user.

If you don't want to enforce that a user should be logged in to able to download a personal data export, you can set the authentication_required config value to false. Setting the value to false is less secure because anybody with a link to a zip file will be able to download it, but because the name of the zip file contains many random characters, it will be hard to guess it.

Translating the notification

You need to publish the translations:

Customizing the mail

You can customize the mailable itself by creating your own mailable that extends Spatie\PersonalDataExport\Notifications\PersonalDataExportedNotification and register the class name of your mailable in the mailable config key of config/personal-data-export.php.

Here is an example:

Then register the class name of your mailable in the mailable config key of config/personal-data-export.php

Customizing the queue

You can customize the job that creates the zip file and mails it by extending the Spatie\PersonalDataExport\Jobs\CreatePersonalDataExportJob and dispatching your own custom job class.

Events

PersonalDataSelected

This event will be fired after the personal data has been selected. It has two public properties:

PersonalDataExportCreated

This event will be fired after the personal data zip has been created. It has two public properties:

PersonalDataExportDownloaded

This event will be fired after the export has been download. It has two public properties:

You could use this event to immediately clean up the downloaded zip.

Testing

You can run all tests by issuing this command:

Changelog

Please see CHANGELOG for more information on what has changed recently.

Contributing

Please see CONTRIBUTING for details.

Security

If you've found a bug regarding security please mail [email protected] instead of using the issue tracker.

Credits

License

The MIT License (MIT). Please see License File for more information.


All versions of laravel-personal-data-export with dependencies

PHP Build Version
Package Version
Requires php Version ^8.0
ext-json Version *
ext-zip Version *
illuminate/filesystem Version ^9.0|^10.0|^11.0
illuminate/queue Version ^9.0|^10.0|^11.0
illuminate/support Version ^9.0|^10.0|^11.0
nesbot/carbon Version ^2.63|^3.0
spatie/laravel-package-tools Version ^1.9
spatie/temporary-directory Version ^2.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package spatie/laravel-personal-data-export contains the following files

Loading the files please wait ....