Cloudron Forum

@girish I totally understand your point. My suggestion was not about Cloudron maintaining a fork (I will explain myself better).

The idea is more about reducing friction for users who want/need a custom build, instead of everyone having to run their own “loose” installation.

Since Mattermost remains AGPLv3 in the open source edition (without the limitations that their official pre-built binaries include), there could be a middle ground:

• Cloudron could allow users to select a custom build in the app configuration, similar to how today you can choose between the Team and Enterprise editions.

• Cloudron can simply add a disclaimer that running a custom build is at the user’s own risk, in case the app breaks or is unsupported upstream.

This way, it remains collective and consistent for all Cloudron users who need this, without putting extra maintenance burden on the Cloudron team.

Mattermost v11 deprecates GitLab SSO – impact on Cloudron users 🥶

Hi all,

Mattermost announced that starting with Server v11.0.0 (October 2025) they will remove the built-in GitLab SSO integration. The current v10.x branch will still be supported for one year, but after that the direct GitLab option disappears (That's what I understand!).

In the open source edition, GitLab has basically been the only built-in OAuth2 IdP option. This has been very valuable because many of us could “bridge” GitLab SSO to other OAuth2 servers, which allowed users to have a passwordless login setup without needing the commercial edition.

It really doesn’t make sense to migrate to a commercial license just to keep a feature that was already free and widely used. I’m sure many Cloudron users currently rely on Mattermost → GitLab SSO for exactly this reason.

So it would be great if Cloudron could either:

provide an official custom image that still includes GitLab SSO, or
make it easier for users to run their own pre-compiled Mattermost builds while keeping Cloudron’s management benefits.

info:
https://forum.mattermost.com/t/mattermost-v11-changes-in-free-offerings/25126

@nebulon just when I was going to start using the OpenAI api (trial period)

@BrutalBirdie In hindsight I read it and you're right, but the bug hasn't been fixed? That's critical!

Rasa is the leading platform for transforming how people interact with organizations through extensible conversational AI

Rasa is an open source machine learning framework to automate text and voice-based conversations. With Rasa, you can build contextual assistants on:

• Facebook Messenger
• Slack
• Google Hangouts
• Webex Teams
• Microsoft Bot Framework
• Rocket.Chat
• Mattermost
• Telegram
• Twilio

Your own custom conversational channels

• Chatwoot Integration

or voice assistants as:

• Alexa Skills
• Google Home Actions

Rasa helps you build contextual assistants capable of having layered conversations with lots of back-and-forth. In order for a human to have a meaningful exchange with a contextual assistant, the assistant needs to be able to use context to build on things that were previously discussed – Rasa enables you to build assistants that can do this in a scalable way.

It would be good to integrate this excellent tool into the cloudron ecosystem

• https://rasa.com/
• https://github.com/RasaHQ/rasa

@shanelord01 I think that wasabi is the cheapest thing on the current market, in terms of price-quality.

https://wasabi.com/cloud-storage-pricing/#cost-estimates

No Charges For Egress or API Requests

Wasabi’s pricing model of $.0059 per GB/mo ($5.99 per TB/month) with no additional

charges for egress or API requests means you don’t pay to access your data.

@nebulon Hello, I edited the nginx config manually on the server... to restrict access to chatwoot's super_admin url... but when I change the config in the app, everything added disappears

location ^~ /super_admin {
    allow 1.2.3.4;
    deny all;
    proxy_pass http://CHATWOOT_INTERNAL_INSTANCE_IP:3000;
}

I think that if you put storage limits for the inbox directly in the cloudron mail configuration, you can prevent it from consuming so many resources, obviously this does not solve the problem you are raising, I don't know how arbitrary it is, either, I'm just providing an idea to encourage a solution.

Ok with the new update chatwoot allows you to put another domain for the help center...

I think this feature needs a web domain alias...