You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running crunz in docker containers but still wanting to use the preventOverlapping feature using a shared volume.
Current Behaviour
Crunz always uses the system temp directory. It also requires on POSIX systems for all crunz jobs to be running in the same execution environment as it checks whether the pid in that file is still running. This prevents using shared file systems but different execution environments.
Proposed Behaviour
No changes to the defaults but adding the ability to change the lock directory and disable the checking of pids (e.g. drop to windows file only mode).
Hello, thanks for issue @IkeLutra.
I like your idea, i even thought about adding symfony/lock component and support other backends such as Redis or memcached, but this need much more work and will be added to v2 of Crunz (probably :).
PR is very welcome, please remember to have v1 as a base branch and v1 as a target brach.
Thanks.
Scenario
Running crunz in docker containers but still wanting to use the preventOverlapping feature using a shared volume.
Current Behaviour
Crunz always uses the system temp directory. It also requires on POSIX systems for all crunz jobs to be running in the same execution environment as it checks whether the pid in that file is still running. This prevents using shared file systems but different execution environments.
Proposed Behaviour
No changes to the defaults but adding the ability to change the lock directory and disable the checking of pids (e.g. drop to windows file only mode).
I have made a first attempt at this on this fork: AgePartnership@0a45f0a
Let me know your thoughts?
The text was updated successfully, but these errors were encountered: