Packaging the enterprise version of Mattermost
-
@Sam_uk It looks like both community and enterprise are the same binary but upgrading requires write permissions on the binary.
This is quite bizzare. It's also documented as such here - https://docs.mattermost.com/install/enterprise-install-upgrade.html . Why does it want to write to the binary!?
-
I was mistaken. Community and Enterprise are different binaries.
- Team edition: https://releases.mattermost.com/X.X.X/mattermost-team-X.X.X-linux-amd64.tar.gz
- wget https://releases.mattermost.com/X.X.X/mattermost-X.X.X-linux-amd64.tar.gz
If you want to upgrade, it will overwrite binary. This is not something we can support. But maybe we can make a new package.
-
@Sam_uk Mattermost say:
"Shut down your instance and replace the mattermost-team-edition image in the dockerfile with mattermost-enterprise-edition image"
*Restart your instance
I don't think they've grasped that Cloudron is slightly more complex wrapper than a simple dockerfile, but it does suggest it should be a fairly straightforward job to fork the Cloudron package?
-
@Sam_uk Yes, correct. The best way forward is to fork https://git.cloudron.io/cloudron/mattermost-app . Then, replace the line in https://git.cloudron.io/cloudron/mattermost-app/-/blob/master/Dockerfile#L11 with the enterprise binary link.
I don't think we are able to create a new package immediately. This requires some testing to know things work and we don't have a license.
But if you are able to do it fork and build and confirm things work, we can look into publishing this.
-
@Sam_uk that's the gitlab.com account. I need your account in git.cloudron.io