-
-
Notifications
You must be signed in to change notification settings - Fork 603
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
Webinterface Backup Export/Import #79
Comments
in what format would you like such a feature ? right now you can easily export the whole database using |
I dont care about compatibility too much. I would just like to have a backup in case i screw up something with Docker and lose all content. Just make it accessible from the webinterface :) |
Ok, a web based backup interface it is! I think this can and will be done but it proably wont be the biggest priority since there are many good options that already work pretty well on the command line. In the meantime you can try this script i personally use for my backups https://github.com/vabene1111/DockerPostgresBackups but be aware that its not really polished/edge case proof |
maybe https://github.com/django-dbbackup/django-dbbackup can be used in combination with #103 and a custom interface to configure/download/restore |
while django-dbbackup in combination with https://github.com/timonweb/django-dbbackup-ui looks really good it appears to be full of bugs where people are having all kinds of problems different databases, special characters in the DB and storage backends. Need to find a better solution as reliability is the number one priority when it comes to backups ... |
ok so i have decided to implement backups using djangos
|
Just wanted to drop by and say this thread was helpful for the following: However, encountered a strange issue. Because of the architecture change, Postgre (db_recipes) was giving me a strange error:
So I ended up using a form of this https://github.com/vabene1111/DockerPostgresBackups to create a dump, then restore it on the new machine. Voila! |
awesome, database migration is always easiest with dumps because it is independet of the version and environment and even if it is you can just change text to get it working. Glad it helped |
Sorry for bumping this old issue, but would a |
that is likely one of the best appraoches but make sure to properly test it before deleting the old DB. There are several foreign relations across the database and loaddata might have a hard time handeling those. I know there is an old discussion from someone who did exactly what you are planning to do, maybe that helps you. |
Thanks, i will attempt to find that discussion, i guess i must have missed it. I will also make a small write up once I (successfully) do so, so hopefully other people would also be able to do it. |
I just successfully exported all my recipes to a zip file via web interface and was able to import them. Is there still any work to be done on this issue? Or are we good to close it? |
yes, the recipes are not a real backup because there are supermarkets, food metadata, autoamtions an much more that should also be included in a real backup. This is planned at some point |
Sorry to add a new comment to this thread. I just updated my docker installation. Then I tried to export ALL recipes. The information window shows the progress of the export but I get no automatic download. The text on the page shows immediately "If download did not start automatically: Herunterladen (Expired)" where download (Herunterladen) is crossed out. If I try to export only one recipe it is no problem. Any idea? |
it should be fixed in the next release - in the meantime, if you hit refresh it will frequently start the download. |
Thanks, I will try :-) |
Can you include some option to export all recipes or even everything into one zip file?
The text was updated successfully, but these errors were encountered: