@nebulon great, thanks so much for this! I should have posted here sooner, I've been scouring the internet for days looking for this. It wasn't listed in any documentation anywhere on containerized versions of Mattermost. Thanks everyone here for all the incredible work you do.

@robi yes, please update to latest cloudron and then update mattermost. there are some db fixes in 7.1 which are required for the upgrade.

@zypA13510 awesome, thanks for testing. The backup folder will only contain the changed files.

@nebulon There is no hint. I'll try it in the Mattermost Community.

thx

@sam_uk yes it does. I created a LAMP app and made it work, here is how:

https://forum.cloudron.io/topic/6368/enable-ldap-authentication-on-mattermost/4

@nj it’s not free, but you can make it work with a workaround. I had to adjust an existing project, but it works now. I put together my changes here, hope it helps:

https://github.com/terehov/Mattermost-LDAP

@ashughes Perfect, that's correct.

Here is the answer:
https://github.com/mattermost/focalboard/issues/2119#issuecomment-1013751739

@robi It's not an issue with cloudron. So I guess as soon as there is a fix by Mattermost it will also land here.
The only action step from @nebulon and cloudron would be to add some tests for boards in future releases.

@robi oh yeah of course, but it is very easy and and I could have actually thought of it myself. 😄

#!/bin/bash cd /app/data/plugins/mail2most ./mail2most -c ./mail2most.conf

This script runs with cron every five minutes to check my mails and send them to the different channels. I have 5 addresses configured and it works fine.

@aizat So, the first one is a bug in mattermost UI. You can see that when you do some actions in the channels UI alone, there are some errors in the browser console. More importantly, I am able to do those actions like unarchive via the CLI just fine.

As for the CLI, this mmctl is a binary that you now have to run on your PC/Mac. You can download it here - https://github.com/mattermost/mmctl/releases . I have put a small note on how to use it here - https://docs.cloudron.io/apps/mattermost/#command-line-tool

@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.