Download the PHP package matthimatiker/command-locking-bundle without Composer
On this page you can find all versions of the php package matthimatiker/command-locking-bundle. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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 command-locking-bundle
CommandLockingBundle
Sometimes you want to ensure that a Symfony console command does not run in parallel. This bundle adds an optional locking feature to all console commands that can be used to prevent parallel execution.
Installation
Install the bundle via Composer:
composer require matthimatiker/command-locking-bundleThen register the bundle in your AppKernel:
<?php
// app/AppKernel.php
public function registerBundles()
{
$bundles = array(
// ...
new \Matthimatiker\CommandLockingBundle\MatthimatikerCommandLockingBundle()
);
// ...
}Usage
Simply pass the --lock option to any command to ensure that parallel runs are prohibited:
app/console cache:warmup --lockIf the command did not terminate yet and the same command is called again (in lock mode), then it is simply skipped and a notice is shown.
The default locking implementation relies on the filesystem and uses Symfony's LockHandler. This avoids parallel execution as long as your application runs on a single system. If you need a distributed lock, then you will have to write your own lock manager.
Custom Lock Managers
A custom lock manager must implement \Matthimatiker\CommandLockingBundle\Locking\LockManagerInterface.
Afterwards it must be registered as service and tagged as matthimatiker_command_locking.console.lock_manager:
my.custom_lock_manager:
class: My\Custom\LockManager
tags:
- { name: matthimatiker_command_locking.console.lock_manager, alias: custom }An alias must be defined together with the tag (custom in this example) and is used to reference
the new lock manager:
app/console cache:warmup --lock=customKnown Issues
When sub-command are called as described in the official documentation, then locking cannot be used for the sub-commands as the life-cycle events are not fired.
