Meridian::Lock::Manager
A simple remote deploy lock. Acquisition is atomic because it relies on
mkdir of the lock directory, which fails on any host filesystem when
the directory already exists. Lock metadata is stored as a small JSON
file inside that directory. SSH, time, and actor dependencies are
injectable for specs.
Constructors
Instance methods
Atomically claim the deploy lock. Raises LockHeld if another caller already holds it.
lock_host
The host that owns the deploy lock - the first web host when present, otherwise the first configured host of any role.
Release the deploy lock. A stale lock is only ever cleared by an explicit release - never silently - and the released lock is announced.
status
Source