3. Mattermost config cannot be updated

Mattermost config cannot be updated

  • C

    Hi team,
    I don't know if you keep in mind that some apps need to update config files to allow some hidden/restricted features for more experienced people, and nowadays I could see that it is not possible.
    I was trying to update config.json to allow upload plugins and the files are read-only. How we can change it ?

    0

  • Hi @csilvav ,

    the config.json of Mattermost is stored in /app/data and should therefore be writable to the admin (the file is created in https://git.cloudron.io/cloudron/mattermost-app/blob/master/start.sh#L7)

    0

  • @csilvav yes, as @fbartels said, you should be able to edit /app/data/config.json using the web terminal. Let us know if that doesn't work. You have to restart the app as well for the changes to take effect.

    0
  • L

    I have a similar issue. My attemts failed to change the config.json file in the terminal. The vi command returns a "readonly file" and I cannot change the permissions. Neither with chmod or with ls. Also mount doesn't work.

    Running the CLT I got this result:
    sudo -u cloudron /app/code/bin/mattermost config set PluginSettings.EnableUploads true
    Error: failed to initialize config store: failed to load: failed to persist required changes after load: failed to write file: open /app/code/config/config.json: read-only file system

    For the mount command I got the report that I don't have the permissions to do that.

    It is a clean new installation. No imports or anything, just the plane Mattermost.

    0
  • M

    @leon said in Mattermost config cannot be updated:

    /app/code/config/config.json

    Edit the config from /app/data/ not /app/code/

    0
  • L

    @murgero thank you. This one works 🙂

    0
    M
     1 Reply
  • M

    @leon Glad to hear! But just an FYI, if you read the comment right above yours, you would have found your answer sooner. Really happy to help though!

    0
  • L

    @murgero now as you said it I see it. I was focussed on the terminal use mentioned in the comment above not about the path. I'll keep that for reading more critically in the future. I'm new to Cloudron but besides that minor issue here everything works great.

    1

  • Keep in mind that most of the good features are Enterprise only. The Team version lacks any permission policy so everyone is able to invite, delete channels and so on. See pricing-feature-comparison. For this reason most projects I know and even the company I work for uses Rocket or Riot/Matrix.

    0
mattermost 3
Log in to reply