Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation about how to backup/restore #606

knarrff opened this issue Mar 3, 2019 · 1 comment

Documentation about how to backup/restore #606

knarrff opened this issue Mar 3, 2019 · 1 comment


Copy link

knarrff commented Mar 3, 2019

Problem you are facing

I would like to backup the current state, and am not sure how to find all 'state' of pretalx, nor how I would go about restoring from it.

Possible Solution

Document this some place.


The current documentation states in multiple places that backups are a good idea (and they obviously are), e.g.:

"you should have a backup of the state before the command run", e.g.:

"While we try hard not to issue breaking updates, please perform a backup before every upgrade."

What I couldn't find is a description of how to do this, except maybe to backup the whole machine. I am a beginning pretalx user, not a developer. So while I installed pretalx and because of that know it uses a DB as backend, I do not know if a backup of the database would be sufficient, or if there is 'state' saved elsewhere as well, and where that all would be, and how to best backup that.

So, I think it would be a good idea to describe how to actually backup the data within a pretalx installation, and in the same document also, how to restore from such a backup.

Copy link

rixx commented Mar 10, 2019

I'm not going to document the how, as this is dependent on the database, OS, isolation, filesystem, etc. But I'll add a note in the docs about the what to include.

@rixx rixx closed this as completed in bfbb76d Mar 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

No branches or pull requests

2 participants