dragon-code / laravel-migration-actions
Performing any actions during the deployment process
Fund package maintenance!
Boosty
Yoomoney
Donationalerts
Requires
- php: ^8.2
- composer-runtime-api: ^2.2
- dragon-code/simple-dto: ^2.5.1
- dragon-code/support: ^6.6
- illuminate/console: ^10.0 || ^11.0
- illuminate/container: ^10.0 || ^11.0
- illuminate/database: ^10.0 || ^11.0
- illuminate/support: ^10.0 || ^11.0
- laravel/prompts: >=0.1
- symfony/console: ^6.0 || ^7.0
Requires (Dev)
- mockery/mockery: ^1.3.1
- nesbot/carbon: ^2.62.1 || ^3.0
- orchestra/testbench: ^8.0 || ^9.0
- phpunit/phpunit: ^10.0
- ramsey/uuid: ^4.0
Suggests
- doctrine/dbal: This package must be installed if you are using Laravel 10.
- dragon-code/laravel-data-dumper: Required if you want to save the execution state using the `schema:dump` console command
- dev-main
- 6.x-dev
- 6.3.2
- 6.3.1
- 6.3.0
- 6.2.2
- 6.2.1
- 6.2.0
- 6.1.0
- 6.0.0
- 5.x-dev
- 5.0.0
- 4.x-dev
- 4.5.0
- 4.4.0
- v4.3.2
- v4.3.1
- v4.3.0
- v4.2.1
- v4.2.0
- v4.1.0
- v4.0.1
- v4.0.0
- 3.x-dev
- v3.2.0
- v3.1.2
- v3.1.1
- v3.1.0
- v3.0.1
- v3.0.0
- v3.0-RC13
- v3.0-RC12
- v3.0-RC11
- v3.0-RC10
- v3.0-RC9
- v3.0-RC8
- v3.0-RC7
- v3.0-RC6
- v3.0-RC5
- v3.0-RC4
- v3.0-RC3
- v3.0-RC2
- v3.0-RC1
- 2.x-dev
- v2.9.0
- v2.8.3
- v2.8.2
- v2.8.1
- v2.8.0
- v2.7.0
- v2.6.1
- v2.6.0
- v2.6.0-rc1
- v2.5.0
- v2.4.0
- v2.3.0
- v2.2.0
- v2.1.1
- v2.1.0
- v2.0.0
- 1.x-dev
- v1.8.0
- v1.7.1
- v1.7.0
- v1.6.0
- v1.5.0
- v1.4.2
- v1.4.1
- v1.4.0
- v1.3.1
- v1.3.0
- v1.2.2
- v1.2.1
- v1.2.0
- v1.1.0
- v1.0.0
- dev-dependabot/github_actions/TheDragonCode/codestyler-5
- dev-6.x-docs
This package is auto-updated.
Last update: 2024-11-27 07:27:29 UTC
README
⚡ Performing any actions during the deployment process
Create specific classes for a one-time or more-time usage, that can be executed automatically after each deployment. Perfect for seeding or updating some data instantly after some database changes, feature updates, or perform any actions.
This package is for you if...
- you regularly need to update specific data after you deploy new code
- you often perform jobs after deployment
- you sometimes forget to execute that one specific job and stuff gets crazy
- your code gets cluttered with jobs that are not being used anymore
- your co-workers always need to be reminded to execute that one job after some database changes
- you often seed or process data in a migration file (which is a big no-no!)
Installation
composer require dragon-code/laravel-deploy-operations
Guidelines for upgrading from previous versions and dragon-code/laravel-migration-actions
and
dragon-code/laravel-actions
packages can be found in this section of the documentation.
Documentation
📚 Read the full documentation at deploy-operations.dragon-code.pro.
Basic Usage
Create your first operation using php artisan make:operation
console command and define the actions it should
perform.
use App\Models\Article; use DragonCode\LaravelDeployOperations\Operation; return new class extends Operation { public function __invoke(): void { Article::query() ->lazyById(chunkSize: 100, column: 'id') ->each->update(['is_active' => true]); // and/or any actions... } };
Next, you can run the console command to start operations:
php artisan operations
📚 Check out the full documentation to learn everything that Laravel Deploy Operations has to offer.
Downloads Stats
This project has gone the way of several names, and here are the number of downloads of each of them:
An upgrade section is available in the documentation for upgrading to a new version.
License
This package is licensed under the MIT License.