Cloudron Forum

@girish I understand, thank you. Looks like they are working on a migration path. So I would prefer to wait before packaging a new one.

I am running Cloudron for 10+ paying customers and counting. One of the reasons how I convince them to use Cloudron is the maintenance of their open source software. All of them use mostly Mattermost. Obviously I’m not too happy that you don’t offer a migration path and make us do the work manually.

I would love to see it too!

@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

Sounds super useful indeed!
We could manage all our users centrally and create mailboxes for them too

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

I was able to fix it by changing the following values in table focalboard_schema_migrations

• version 15 -> 11 (I figured that's the current version)
• dirty 1 -> 0

Thank you, guys.
Unfortunately, it didn't fix it for me, since plugins were already enabled.

Then I found this in my logs:

Jan 18 11:25:23 {"timestamp":"2022-01-18 10:25:23.926 Z","level":"error","msg":"Not activating plugin because diagnostics are disabled","caller":"app/plugin_api.go:928","plugin_id":"com.mattermost.nps"}

So I enabled diagnostics. However this was the result (not sure if its related to this update):

Jan 18 11:28:35 {"timestamp":"2022-01-18 10:28:35.229 Z","level":"error","msg":"Unable to activate plugin","caller":"app/plugin.go:142","plugin_id":"focalboard","error":"error initializing the DB: Dirty database version 15. Fix and force version."}

Hey there,

does anybody else experience the same?
We were using Mattermost Boards (introduced in V6) and they disappeared after the last update to 6.3.0.

I can still find the setting and tried disabling and enabling (hoping that would set a flag in DB). Unfortunately, it did not help.

I guess it would make sense to add boards to the tests too.

Best

Eugene

I'll be in Berlin next week (Mon-Thu). But I guess it's too short of a notice

@girish The reason could be that it's quite stable already. We use their commercial SaaS version that uses that in the background but provides a nice UI and it works like charm. I guess they are more focused on supporting new devices and updating their OS, which happens regularly.
You can check their forums. I mean, those guys ported Docker to ARM in the first place.

Yes, that would be amazin indeed!

+1 for Zammad

@girish As far as I know you can even "Upgrade to Enterprise Edition" inside of a team version. There is a button for that in the system console.

In regards to LDAP there are two ways: either as part of the enterprise version, or in combination with a (e.g. selfhosted) Gitlab.
Or if Cloudron should happen to behave like Gitlab or... well... something like
https://github.com/Crivaledaz/Mattermost-LDAP

Hey there,

as you probably know Matteromst offers LDAP with the enterprise edition. I was wondering if there is a way to make it work with the cloudron LDAP?
What are the necessary steps?

Thanks

cheers

Eugene

@nebulon Exactly. So Chatwoot basically expects another Relay to receive and parse an e-mail and forward the parsed json result to chatwoots' webhook. This seems to be using of RoR "Action Mailbox Basics" in the background.

Since Cloudron has a build-in mail server, I was wondering if it is possible to facilitate this functionality here. I couldn't quite figure out what cloudron uses. For outbound, you seem to be using Haraka, or is it for both?

@fbartels Thank you very much. I guess I'll try the official way. Thanks for pointing out the functionality of add-ons.

Dear community,

I really hope somebody could explain to me the bits and bolts of Cloudron in terms of app backups because I couldn't figure it out myself with the docs.
Right now we run our own instance of Mattermost on top of Postgres and store our binary files in S3 (on Caprover). We plan to move all our apps to Cloudron.

I am aware that on Cloudron the default setup is with MySQL and the file storage instead of S3 and the easiest way is probably to export from our existing instance in import into Cloudron.
However, I would like to keep the files in S3 and maybe even continue to use Postgres, if possible, which is also available on Cloudron. The easiest way to achieve this is probably to adjust the config.json file of Mattermost.

My question is: Since I would like to facilitate backups and other features provided by Cloudron, I would like to understand how the backups work under the hood: Would it be enough to just create a database in Postgres and adjust the URI in config.json, or would it indeed be better to migrate to MySQL? And especially how to proceed with the binary files and S3, which I would like to keep there. Or should I somehow copy them to the file system? Or keep them in S3 without backups through Cloudron?

Thanks a lot!

cheers

Eugene