Packaging the enterprise version of Mattermost
-
I ordered the Non-Profit enterprise version of Mattermost.
I now see in this thread that the Enterprise/Free versions would require separate packages?
We get this error: Mattermost was unable to upgrade to Enterprise Edition. The Mattermost system user cloudron does not have write access to the necessary binary file.
Would you consider packaging the Enterprise version in addition to the free version? Or is there a workaround we can apply to the existing package @staff
-
@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.
-
How annoying. Could you have a look into packaging the Enterprise version for us to see what would be involved?
-
@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.
-
@girish We get this unspecified error when we try to fork?
-
@Sam_uk oh forks are limited by default because of spam. What is your id on gitlab?
-
@girish could you give access to
https://gitlab.com/samuk1 please
-
@Sam_uk that's the gitlab.com account. I need your account in git.cloudron.io
-
@girish Could you give access to https://git.cloudron.io/lesteak please
-
@Sam_uk you should be good to go!
-
Thanks @girish Once we have it working and somewhat tested what would be the next steps? I can give you access to our Cloudron instance for some further testing?
-
@Sam_uk sounds good!
-
This post is deleted! -
@Sam_uk OK this seems to build and accept my licence. I've sent a user invite to support@cloudron.io so you could have a poke at it and see if you're happy to add to the appstore.
-
@Sam_uk https://git.cloudron.io/lesteak/mattermost-enterprise/ is the repo correct?
-
@girish Yes that's correct
-
@Sam_uk Will take us a bit to get to it (after 7.4 probably), but I think you can continue running your custom build since they only release once a month or so. We will get to this at some point.
-
@girish Great. You wouldn't anticipate any security implications from the change of binary?
-
@Sam_uk hopefully not but I don't know what the mattermost enterprise specific settings are. Do they offer any diagnostic inside the admin dashboard?
