-
Notifications
You must be signed in to change notification settings - Fork 28
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
Enhancement Request - Backup/Restore of settings #728
Comments
These are the flask database migrations. You can try these steps from https://github.com/aaronwmorris/indi-allsky/wiki/Database-migrations#fixing-broken-migrations
|
I got to the same point in a slightly different way. I reconnected the old disk, updated indi-allsky and re-run the export. That has now worked and I'm up and running. In retrospect, your method would have been slightly quicker. :) Nevertheless, if you're interested, my request for the enhancement is still a valid one (he asked hopefully!) |
Your method was going to be my next suggestion, which is the best way. I will write up a backup/restore procedure. |
I did run into the same Error: Can't locate revision error when I next updated the new system from the GIT master - even after updating using 'my method', so I still had to use the |
It is only a problem if the last database schema does not reflect what is in the DB. If you upgraded before moving systems, you should be fine. |
Hi Aaron |
Not yet. I will get to it very soon. |
This is my first pass at an informational page on backing up indi-allsky: https://github.com/aaronwmorris/indi-allsky/wiki/Backup-and-Recovery I am also planning on writing a script to create a unified tar file of all of the files necessary to backup. |
That new page looks good, Aaron. Script would be good (and I'd be happy to test - at least to a VM and back)
I count 5 areas, not 4 (OK - so one is optional) :) |
Having moved to a new (larger) ssd, I had to go through the pain of a database migration from an earlier build of indi-allsky to a newer build just to transfer all the settings from one instance of indi-alllsky to another.
Is there a way to add a indi-allsky settings backup or export to (say) the Utilities page that could then be used as an import on the new instance? Perhaps in a json format or similar?
Thinking this would simplify a number of tasks - particularly rebuilding an indi-allsky camera that's had a disk or storage failure. The ability to save this backup offsite using the file transfer side, or a simple copy to USB stick would pay for itself the first time it's used.
The text was updated successfully, but these errors were encountered: