Replies: 2 comments
-
Hmm, that's odd for sure -- when updating from 4.x to 5.x, did you first make sure to update to the most recent 4.x? Beyond that, I don't have many ideas. 🙈 |
Beta Was this translation helpful? Give feedback.
-
Yeah I had updated to the latest version of 4 with no problem. To do that I just pulled the latest docker container with tag 4-alpine (docker-compose down, docker-compose pull, docker-compose up) Is there a way to backup the entire contents of the database and then re-load them into a fresh 5-alpine install? I know I can export the posts and content but not sure about the users as well. |
Beta Was this translation helpful? Give feedback.
-
Hey I've been working on updating my ghost instances from an older v4 to the latest v5. I am already running mysql (I read that there are issues switching from mysqlite but that doesn't apply to my case)
Instructions and some issues I've read say to update to the latest minor version which I did fine but then when going from tag
4-alpine
to5-alpine
, it first fails to connect to the database. But if I manually specify the database connection info via environment variables, the database gets wiped (see logs below of it creating all new tables in mysql). Luckily I have backups so I restored back to one of those and tried updating the tag to5.0.1-alpine
which worked completely fine. I then stepped through each minor version up to5.5.1-alpine
and they all worked fine. I then went for it and upgraded to5-alpine
which broke once again, failing to connect to the database. When I manually specified the database connection params, it created the new tables once again.(I have removed sensitive creds and the name of my site/url)
original docker-compose.yml
new docker-compose.yaml
original docker-compose.yml
Here's the first logs, failing to connect to the database
And when using the second compose yaml, wiping the db:
Beta Was this translation helpful? Give feedback.
All reactions