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
There is no documented method of how to restart the server when running in a container in such a way that it preserves the database.
This is non-trivial because just killing the server and removing the container and starting it again breaks because if you mount it to data folder with an existing database, it "gets mad" and breaks because it tries to run the migrations and create the admin {insert correct word here} again and this must be unique.
Bug Report
Expected behavior:
If I for some reason need to restart the server and remount it to the same data directory because I want to continue to have access to all previously generated data, I have some instructions about how to do this.
Actual behavior:
I'm on my own.
The text was updated successfully, but these errors were encountered:
Opening a new issue
Specify type:
Bug severity (if applicable):
Description:
There is no documented method of how to restart the server when running in a container in such a way that it preserves the database.
This is non-trivial because just killing the server and removing the container and starting it again breaks because if you mount it to data folder with an existing database, it "gets mad" and breaks because it tries to run the migrations and create the admin {insert correct word here} again and this must be unique.
Bug Report
Expected behavior:
If I for some reason need to restart the server and remount it to the same data directory because I want to continue to have access to all previously generated data, I have some instructions about how to do this.
Actual behavior:
I'm on my own.
The text was updated successfully, but these errors were encountered: