@mtd-sales let us know if you have trouble importing/exporting via mattermost CLI. One thing is that you want the version of mattermost you are running now and the one on Cloudron to match. On Cloudron side, if you look at the https://git.cloudron.io/cloudron/mattermost-app/-/blob/master/CHANGELOG it will tell you the package version. Then, you can change the package version in the URL bar of your dashboard when installing an app (i.e click the mattermost app in App Store and then change the version field in the URL). As for storing things in S3, I think you have to decide whether you prefer files stored externally or on the server itself. The main difference is with respect to backups. If on server, Cloudron will include them in the backup and restore will also work properly. But if it's in an external service, the backup won't include them and thus restore might be complicated. Like if you restore to a mattermost from a week ago, I am not sure how you roll back S3 storage to a week ago (especially, if you had deleted files in the middle). I guess the compromise you make depends on your use case.

@girish thank you for the details and understanding! Yes, I'm exactly worrying about reliability and that the files can get overwritten randomly.

@murgero thank you !

@potemkin_ai yes, correct, letting the mattermost folks know would be the next step since this does not look like a packaging issue.

@robi

@girish thank you. I meant only server part of course - mobile one is easy to be handled by myself Did the post. What’s happening next?

@tomw thanks for the update! I will make the default value higher in the next release.

@subven Thank you! I had not seen those docs It turned out that the Docker image of Mattermost used PostgreSQL, whereas on Cloudron if I'm not mistaken MySQL is used. I tried converting migrating the PostgreSQL database to MySQL but it was a bit of a headache, so I have gone down the conventional route of using Mattermost's bulk export/import.

@marcusquinn that plugin was simple 1 to 1 calls directly initiated from the Mattermost ui. For that we leveraged the existing (unfinished) WebRTC integration into Mattermost. Because of this the first version of kwmserver had an api that was compatible to Janus (which was a requirement to the native WebRTC back then). The page you linked to was/is the explanation how to install our Mattermost packaging (https://documentation.kopano.io/kopano_mattermost_manual/webmeetings.html was the meanwhile replaced page for the plugin). We originally had a partnership with Mattermost, but especially compared to our Groupware pricing Mattermost was too expensive for most of our customers. Currently there is no direct integration of Meet into Mattermost. We simply have too few customers using Mattermost to warrant the invest ourselves, but there was external interest in doing something, for example at https://github.com/Kopano-dev/meet/issues/9.

Wow, what a horrible design for maintenance. Thanks for finding it. I'm not interested in editing the DB. As long as I find where the files are, I can clean those up without removing the messages and references. Looks like I found just that at /app/data/files/. A visit via the new File Browser in the Cloudron App Config/Console easily finds the few large attachments. Another thing I noticed is that MM generates preview and thumbnail images for some reason, which more than doubles the storage requirements for each image uploaded. Some of the generated preview images are larger than the original uploads

For new installations, I already fixed it - https://forum.cloudron.io/topic/2441/mattermost-package-updates/14 to disable EnableFile to false by default. For existing ones, users have to edit the file manually.

Thank you, that works. But why I cant upload plugins via GUI although I have set the right setting (https://screenshots.x-mailer.de/u/smichna-2020.09.15-1TsnjG54.png).

Hi @austinsonger is there anything in the app logs regarding that error?

thank you for your replies. I found the error in a complete different field. A custom emoji crashed the bulk export. After deleting this I could perform the export as planned and the import to Cloudron worked as described in the documentation. Still thank you for your efforts.

@katarina You can use the mattermost CLI tool to export from your existing installation and then import to Cloudron installation. I have added the instructions to our docs here - https://cloudron.io/documentation/apps/mattermost/#migration

ahh, thanks very much! that makes sense