hedgehog-lab / laravel-mutex-migrations
Run mutually exclusive migrations from more than one server at a time
Maintainers
Package info
github.com/hedgehoglab-engineering/laravel-mutex-migrations
pkg:composer/hedgehog-lab/laravel-mutex-migrations
Requires
- php: ^8.2
- illuminate/console: ^10.0 | ^11.0 | ^12.0
- illuminate/contracts: ^10.0 | ^11.0 | ^12.0
- illuminate/database: ^10.0 | ^11.0 | ^12.0
- illuminate/support: ^10.0 | ^11.0 | ^12.0
Requires (Dev)
- orchestra/testbench: ^8.0 | ^9.0 | ^10.0
- spatie/fork: ^1.2
README
Run mutually exclusive migrations from more than one server at a time.
Using Laravel's functionality for Atomic Locks, this package extends the built-in MigrateCommand class to allow migrations to be run safely when there is the chance that they may be run concurrently against the same database.
Installation
Install the package with:
composer require hedgehog-lab/laravel-mutex-migrations
Optionally publish the package config file:
php artisan vendor:publish --tag=mutex-migrations-config
Usage
Running a mutex migration using the default database store requires the existence of a table to store cache locks. If it does not exist the command will automatically fallback to a standard migration.
php artisan migrate --mutex
If two or more migrations happen to run concurrently, the first to acquire a lock will block the next one from running until it has finished, or until the lock times out - after 60 seconds, by default.
Testing
./vendor/bin/phpunit