Download the PHP package myparcelcom/concurrency-safe-migrations without Composer
On this page you can find all versions of the php package myparcelcom/concurrency-safe-migrations. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download myparcelcom/concurrency-safe-migrations
More information about myparcelcom/concurrency-safe-migrations
Files in myparcelcom/concurrency-safe-migrations
Package concurrency-safe-migrations
Short Description Provides an artisan command that runs migrations but prevents execution at the same time
License Apache-2.0
FAQ
Example:
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 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.
Informations about the package concurrency-safe-migrations
Concurrency-safe migrations for Laravel
Overview
This library ships the command migrate:safe for Laravel which executes the migrate artisan command in concurrency-safe manner using the Laravel atomic locks.
Installation
First, include the myparcelcom/concurrency-safe-migrations package in your composer dependencies:
Simply register the MigrateSafe command with your console Kernel:
Configuration
All options available with the migrate command can be passed to migrate:safe too. In addition, you can configure the atomic lock settings too:
--lock-ttl- pass custom maximum lock ttl (in seconds). Themigrate:safewill automatically release the lock once done. However, it is useful to put some ttl in failure cases where the container dies and lock is not released. Default value is 60 seconds--cache-store- select a specific Cache store. When omitted the default cache store is selected. The cache store is required to work with atomic locks.--key-id- enter custom cache lock key. When omitted theAPP_NAMEand current application environments are used to compose a key
Background
Running migrations using migrate:safe assures that your application will not execute migrations at the same time. This could be a problem if you want to automate running migrations for your app but for whatever reason you cannot assure that the migrate command will be ran only once per deployment.
An example application is deploying a Laravel application on Kubernetes using Flux. Flux reconciles changes from Git in declarative way. Therefore, it becomes difficult to activate migrations upon deployment using a Job.
migrate:safe allows developers to attach init containers to deployment pods and only one will execute the migrations.
