mirror of
https://github.com/dehydrated-io/dehydrated.git
synced 2026-03-08 00:50:01 +01:00
Add lockfile #8
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @lukas2511 on GitHub (Dec 8, 2015).
If this script is used inside a cronjob it may interfere with a user using the script, so i think it would be a good idea to have some sort of lock-file to make sure it's at least not signing the same domain at the same time, or maybe even that it's not running at the same time.
@alexandresobolevski commented on GitHub (Feb 23, 2017):
Hi @lukas2511 . Could I ask you to elaborate on what exactly is protected. My situation is that I wish the script to be accessible asynchronously to renew certificates of some of my domains. It will be accessed from different processes - possibly at the same time but renewals are performed for different domains. What are the repercussions if I use the
no-lockargument?Thanks a lot.
@lukas2511 commented on GitHub (Mar 27, 2017):
@alexandresobolevski sorry for the late response: locking basically protects the script to write to the same files at the same time. if you register an account key first and control the script externally later on using the
-d domain.tld -d www.domain.tldoptions there shouldn't be any remaining conflicts, but you should never use the no-lock option when running with a domains.txt