kaliop / kaliop-lock-command-bundle Goto Github PK

"Lock" is a generic term and can mean many things in the context of executing a console command.

What this bundle is really doing is really "preventing concurrent execution".

Maybe we could find a better, short term to define the concept ?

If a command crashes, my gut feeling is that it will stay locked forever.
it would be nice to have an 'unlock' command to allow removing the locks.
Even better: to have a cronjob that automatically removes locks that are older than X days/hours

[Composer\Repository\InvalidRepositoryException]: Some branches contained invalid data and were discarded, it is advised to review the log and fix any issues present in branches

Reading composer.json of kaliop/lock-command-bundle (master)
Skipped branch master, Invalid package information:
extra.branch-alias.dev-master : the target branch (master) must end in -dev

It would be nice to be able to preventively lock a command, eg

php app/console kaliop:command-lock:lock mycommand:that:does_stuff

In the scenario where one executes commands on multiple, separate servers, locking via filesystem can be not effective.

To allow locking commands across all servers, a shared-lock implementation is required.

Simfony provides this via the Lock component, which is available since version 3.4, so it makes a good candidate for replacing the LockHandler.

Moreover, LockHandler is deprecated and then removed in Sf 4