-
Notifications
You must be signed in to change notification settings - Fork 187
Migrating from 2.2-95 to current version #316
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
Comments
Yes. There are alembic migration scripts that are called on startup to migrate the database. I would still highly recommend making a database backup first, given how old the revision you are currently running is. |
I take it that this does migrate the data from elasticsearch as well? |
It regenerates the image signature data again. It takes a bit of time and CPU to do, but is done when the site is online. No data is lost (elasticsearch didn't really store any data that couldn't be computed again) so you can safely delete the index even before the migration. |
Ok so I'm done, here's what I did:
|
Hey there, I'm running an old szurubooru instance on http://gondbooru.lett.at/ and I want to upgrade to the new docker version, my main question is: how do I migrate to the new version? Can I just point the docker container to the old postgres DB and have it migrate automatically? And if that's not possible, export and reimport all the posts/users and so on?
The text was updated successfully, but these errors were encountered: