Hi guys, creator of lockable here - the easiest way to think of lockable is as `flock` for when you don’t have a shared file system. You can use it to control concurrent access to resources or to ensure only a single instance of a process runs at any given time.
Your processes can acquire, refresh and release locks via simple HTTP requests, so it’s language/framework agnostic. E.g. with `curl`:
$ curl https://lockable.dev/api/acquire/my-lock-name
{
"response": true //or false, if the lock wasn’t available
}
$ curl https://lockable.dev/api/release/my-lock-name
There’s also a Python client[0], which makes using the service a more pleasant experience.
Feel free to play around, the free tier is fully functional. Happy to hear any feedback you might have.
Your processes can acquire, refresh and release locks via simple HTTP requests, so it’s language/framework agnostic. E.g. with `curl`:
There’s also a Python client[0], which makes using the service a more pleasant experience.Feel free to play around, the free tier is fully functional. Happy to hear any feedback you might have.
[0]: https://docs.lockable.dev/en/latest/python-client/