Add a backup / restore procedure in the documentation #17790
Replies: 3 comments 3 replies
-
|
The metadata database should be the only thing you need to backup. As for how to backup the database, that would depend on which database or service you're using. |
Beta Was this translation helpful? Give feedback.
-
|
I agree. This product needs a well-defined (and supported) backup/restore procedure. For example, one (apparently) supported way of installing this product is via Docker Compose. This kind of installation creates a local database using a docker volume. Anyone that's tried, knows what a problematic issue it is to backup and restore a docker volume. This has nothing to do with which backend we selected for our DB. If the supported solution is to run |
Beta Was this translation helpful? Give feedback.
-
|
Good points. Anyone is free to submit a documentation pull request to improve this. I'd be happy to review. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I do not find any information about backup and restoration processes.
I do not know if I only have to backup the database or if other files (likes settings or custom user files ) that may exist on the filesystem need to also be saved.
A little chapter in the documentation on this topic would be great.
Regards,
Benjamin
Beta Was this translation helpful? Give feedback.
All reactions