Backup / Restore functionality #5631
samwathegreat
started this conversation in
Polls
Replies: 1 comment
-
|
Just some thoughts.. Sure this would be nice - but essentially given that this is a docker project, the backup procedure is as simple as zipping up the working folders. As for databases where not using sqlite, that's up to the user to backup too. If the app were to have a backup function, it would just be doing the same thing - zipping up folders and dumping sql. The problem comes from restoring; where the db connection is defined in compose config env vars, not in the backup file. ie restoring a postgres instance to a new sqlite instance is likely going to fail. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, all. Long time, very appreciative user here! NPM is fantastic!
Unfortunately, it would seem that one of the absolute most-requested features is still missing -- Backup & Restore functionality.
There are multiple posts addressing the lack of this functionality, but I haven't seen any intention or committment to actually implement this highly-desired feature. Many posts/threads suggest that implementing this would take little effort & time.
So, just to get a clear picture of the amount of value that the community would rank having backup / restore functionality built into to NginxProxyManager, here is a poll:
Do you feel that this is one of the most desired features that would put NPM ahead of other solutions like Caddy or NPM Plus?
11 votes ·
Beta Was this translation helpful? Give feedback.
All reactions