Packaging the enterprise version of Mattermost

[girish]

@Sam_uk I have pushed a new package now (as unstable). After you update, edit /app/data/edition.ini . Change it to enterprise and restart the app. Let me know how it goes.

[Sam_uk]

Thanks!

I updated my dev.mattermost instance and then looked for /app/data/edition.ini but couldn't find it. Do I need to do a fresh install?

[girish]

@Sam_uk are you on package version 1.82.0 ?

[Sam_uk]

It says .mattermost.cloudronapp?version=1.81.0 .

Just upgrading to latest now, it wasn't showing the update earlier

[Sam_uk]

That all seems to work, thanks!

Now I just need to transition my current /live site (custom app) to start using the 'mainline' Cloudron app packaging again?

Any guidance on how to best do that?

[girish]

@Sam_uk first make sure the mattermost versions match. after that, I think you take a backup . then, import the backup into a fresh mm installation .

[Sam_uk]

So I need to downgrade the /dev again so that versions match, do the import, then upgrade it?

[girish]

@Sam_uk the package version don't need to match, only the mattermost version . Cloudron package is using mattermost 9.4.1 . Note that I am assuming here that the Cloudron package and the custom package you are using are similar. Maybe you can compare the code and double check.

[Sam_uk]

So i install the old version like this

[samuk]

I'm trying to import the backup from the old custom version into the new version appstore version. The version numbers match but I get an error "Error : External Error - incorrect header check" what does that mean please?

[girish]

That looks like a zlib error. Are your backups encrypted? What storage are you using? Maybe you can download the backup file locally and try to extract it just to test.

[Sam_uk]

Just to confirm this worked in the end. Thanks for the support

[CBCUN]

@Sam_uk said in Packaging the enterprise version of Mattermost:

Just to confirm this worked in the end. Thanks for the support

Hi,

i have the same error on a other situation. Would you share your solution with us, please.

Greetings

[Sam_uk]

@CBCUN It was an incorrect passkey in my case. Using the correct one worked.