-
Notifications
You must be signed in to change notification settings - Fork 211
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
Upgrading from mattermost-docker #40
Comments
Hello, I had pretty same issues.
and got error on cloning tianon/docker-postgres-updated
Thankyou :> |
I've provided another way to migrate from |
Hey, i had similar issue, but i was coming from PG 10.8, |
Hello @jasonblais , @mrckndt
As mentioned in mattermost/mattermost-docker#529 I did my tests to migrate from MM 5.31 to 5.32.1 with the migration script.
I have few remarks about the script :
So I suggest that the version must be fixed in the script or export before running it.
# - MM_VERSION=5.31
in the docker-compose.yml and in the Dockerfile you have : ARG MM_VERSION=5.31.0the
sed
command will write5.32.1.0
instead of5.32.1
so what do you think about reading the value directly from the Dockerfile instead of the docker-compose.yml file ?
Then the last step, when the migration is done, how to swith from the old directories/files structures to the new one with the new repo ? Is it possible to change the path for the volume directly in the .env file and that's all ?
Thank you very much.
Best regards,
The text was updated successfully, but these errors were encountered: