Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Solved Changes to db setting in config.json are not persisting

    Mattermost
    2
    4
    31
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      shrey last edited by

      On a fresh Mattermost install, i tried to edit the config.json file, via the File Manager, to connect to a remote Postgres database as the primary database (https://docs.mattermost.com/configure/environment-configuration-settings.html#data-source).

      But, as soon as i restart the app, the changes get overwritten by the default mysql config.

      Need some help to figure out the issue here.

      girish 1 Reply Last reply Reply Quote 1
      • Topic has been marked as a question  S shrey 
      • girish
        girish Staff @shrey last edited by

        @shrey it's not possible to use a different database other than the one that the package pre-configures. This is true for any app and not just mattermost. Databases are part of the application lifecycle - update/restore/backups etc. It's not possible to make it external.

        You should be able to configure other settings though.

        S 1 Reply Last reply Reply Quote 0
        • Topic has been marked as solved  girish girish 
        • S
          shrey @girish last edited by

          @girish Oh, didn't know that.

          girish 1 Reply Last reply Reply Quote 0
          • girish
            girish Staff @shrey last edited by girish

            @shrey Database and email are "special". It's part of app packaging and cannot be changed across apps.

            https://docs.cloudron.io/packaging/addons/ are the services provided by Cloudron.

            We do make things optional on a case by case basis. For example, email can be set as optionally configured in the package. Next release we will make turn configuration option. These are of course easier to do than making database configuration optional because they are not part of backups/updates.

            1 Reply Last reply Reply Quote 1
            • First post
              Last post
            Powered by NodeBB