Persistent configuration with automatic backup/restore handling #42
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Implements automatic backup and restore logic for renew.cfg to ensure user configuration is preserved across VIB upgrades or accidental deletion. - Stores backups in /etc/w2c-letsencrypt, a persistent location. - Rotates backups: keeps latest (.bak) and previous (.bak.old) versions. - Restores renew.cfg
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces a configuration persistence mechanism in the
renew.shscript to ensure that user configurations are not lost during server reboots or VIB upgrades. The changes include logic for backing up and restoring therenew.cfgfile, as well as handling multiple backup versions.Configuration persistence enhancements:
renew.cfgfile to/etc/w2c-letsencrypt/renew.cfg.bakand maintain an older backup version (renew.cfg.bak.old) to ensure configuration safety when configuration changes are made.renew.cfgfile from the latest backup if the main configuration file is missing but a backup exists.