Migration to Cloudron from a Postgres backed instance
-
Hello,
I'm currently trying to migrate my mattermost instance to Cloudron but I have an issue with all the attachments.
I used themattermost bulk export/importway as my current instance is using PostgreSQL. I succeeded to import all my messages (private or not), users, channels etc... but missing all the attachments.
I did copy my data folder from my original server to theapp/data/files/folder of my cloudron instance (there is some ~20Go of attachments in 55k files inside a tree of 66k folders hopefully backups will be ok) my issue is that those files aren't seen by mattermost (either during the import or after)Some ideas of what I could be doing wrong?
-
@cvachery I would hold off a bit on this. Current mattermost package uses MySQL but we have been told that it is getting deprecated and move to PostgreSQL is in order. I guess you have already seen https://forum.cloudron.io/topic/9707/mattermost-v8-0-and-postgresql/ since you commented there.
-
Yes I did but it not "urgent" but I need to move my mattermost instance ASAP so cloudron it is
I did see it but as I don't when it will be available I decided to move on. I guess I will be able to move from MySQL to PostgreSQL anyway in the future
And to answer my own question I missed a flag in the command
--import-path /app/data/files/which tells mattermost to look in this folder.It could be nice to add it to the documentation and in the same way edit the command to add the new path
/app/code/EDITION/bin/mattermostwhere EDITION can be eitherteamorenterprise -
And to finish on the migration issues encountered :
- My users lost their passwords during the migration (simply need to do forgotten password but still an inconvenience)
- Couldn't migrate custom emoji (had to delete them from the jsonl file
- User avatars were not migrated
- All private messages are now unread
-
Yes I did but it not "urgent" but I need to move my mattermost instance ASAP so cloudron it is
I did see it but as I don't when it will be available I decided to move on. I guess I will be able to move from MySQL to PostgreSQL anyway in the future
And to answer my own question I missed a flag in the command
--import-path /app/data/files/which tells mattermost to look in this folder.It could be nice to add it to the documentation and in the same way edit the command to add the new path
/app/code/EDITION/bin/mattermostwhere EDITION can be eitherteamorenterprise -
And to finish on the migration issues encountered :
- My users lost their passwords during the migration (simply need to do forgotten password but still an inconvenience)
- Couldn't migrate custom emoji (had to delete them from the jsonl file
- User avatars were not migrated
- All private messages are now unread
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login