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
I'd like an option to not generate backups when running dehydrated --account, because currently the backups just don't get automatically cleaned up otherwise. And I really have no use for these backups.
Why not just delete the backup files if I don't need them?
Well not only is that inconvenient, but in my case, I'm developing a Docker image integrating dehydrated with a declarative config. Ideally, a user of my image should be able to change their ACME account email without having to manually go into the Docker volume to delete these backup files. I could delete them automatically, but dehydrated also outputs a message saying the file was backed up, so deleting them would make that message misleading.
The text was updated successfully, but these errors were encountered:
Suggestion
I'd like an option to not generate backups when running
dehydrated --account
, because currently the backups just don't get automatically cleaned up otherwise. And I really have no use for these backups.Here's the line that backs up the file:
dehydrated/dehydrated
Line 1657 in 4fd777e
Why not just delete the backup files if I don't need them?
Well not only is that inconvenient, but in my case, I'm developing a Docker image integrating
dehydrated
with a declarative config. Ideally, a user of my image should be able to change their ACME account email without having to manually go into the Docker volume to delete these backup files. I could delete them automatically, butdehydrated
also outputs a message saying the file was backed up, so deleting them would make that message misleading.The text was updated successfully, but these errors were encountered: