This package allows you to download, export and import your application's database backups.
- Store your local database in a file
- Non-productive developer machines can download the live server database
- A central backup server can collect backups from multiple live servers
- Download and optionally import databases from a server
- Import existing database files
- Export the local database to a file
- User authentication through Laravel Sanctum tokens
- Transport encryption using Sodium
Run the following command for an interactive shell
php artisan protector:import
To download and import the server database in one go, run
php artisan protector:import --remote
When used with other options, remote will serve as fallback behavior.
To import a database you downloaded earlier, run
php artisan protector:import --file=<your backup file>
To import the latest existing database file, run
php artisan protector:import --latest
To learn more about import options run
php artisan protector:import --help
By default dumps are stored in
storage/app/protector
To save a copy of your local database to your local disk, run
php artisan protector:export
Find below three common scenarios of usage. These are not mutually exclusive.
If you only want to store a copy of your local database to a disk, the setup is pretty simple.
Install the package via composer.
composer require cybex/laravel-protector
You can optionally publish the protector config to set the following options
fileName
: the file name of the database dumpbaseDirectory
: where files are being storeddiskName
: a dedicated Laravel disk defined in config/filesystems.php. These can point to a specific local folder or a cloud file bucket like AWS S3
artisan vendor:publish --tag=protector.config
You can now use the artisan command to write a backup to the protector storage folder.
php artisan protector:export
By default the file will be stored in storage/protector and have a timestamp in the name. You can also specify the filename.
You could also automate this by
- installing a cronjob on linux
- running it when you deploy to your server
- creating a Laravel Job and queueing it
php artisan protector:export --file=storage/database.sql
This package can run on both servers and client machines of the same software repository. You set up authorized developers on the server, and give them the key for their local machine.
Install the package via composer.
composer require cybex/laravel-protector
In your User model class, add the following trait.
use Laravel\Sanctum\HasApiTokens;
class User extends Authenticatable
{
use HasApiTokens;
...
}
Publish the protector database migration, and optionally modify it to work with your project.
php artisan vendor:publish --tag=protector.migrations
Run the migration on the client and server repository.
php artisan migrate
You can optionally publish the protector config to set options regarding the storage, access and transmission of the files.
php artisan vendor:publish --tag=protector.config
Run the following command to receive
- the public key to give to your server admin
- the private key to save in your .env file
php artisan protector:keys
Your server admin will then give you the token and server-url to save in your .env file. Unless specified otherwise in your software, the .env keys are
PROTECTOR_AUTH_TOKEN=
PROTECTOR_SERVER_URL=
Do not give your private key to anyone and keep it protected at all time
See Usage on how to import the remote database.
Downloaded database dump files are stored unencrypted
Make sure that the server is accessible to the client machine via HTTPS.
When one of your developers gives you their public key from the previous step, you can authorize them with:
php artisan protector:token --publicKey=<public key> <user id>
You will receive the token and url to give back to the developer, who has to save them in their .env file.
The developer can then download and import the server database on their own.
You can develop a custom client that can access and store remote server backups. The servers can be different Laravel projects that have the protector package installed.
See the previous chapter on how to give your backup client access to all servers. The backup client will need an according user on each target server.
- All the backup users on the target servers will have the same public key from the client
- For each target server, the client will store the according url and token
See cybex-gmbh/collector for an example implementation.
Please see CONTRIBUTING for details.
If you discover any security related issues, please email webdevelopment@cybex-online.com instead of using the issue tracker.
The MIT License (MIT). Please see License File for more information.
This package was generated using the Laravel Package Boilerplate.