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


  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

Cloudron Forum

Apps | Demo | Docs | Install

Mattermost v8.0+ and PostgreSQL

Scheduled Pinned Locked Moved Mattermost
11 Posts 4 Posters 148 Views
    • 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.
  • C Offline
    C Offline
    c0decafe
    wrote on last edited by
    #1

    The latest mattermost release now recommends PostgreSQL over MySQL and the project is generally planing to phase out support for MySQL.

    Any plans to migrate the cloudron mattermost app to PostgreSQL in the near future?

    Some new features such as AI bots are only available with PostgreSQL instances., and we would love to be able to leverage that as soon as possible.

    Just to plan accordingly, thanks!

    girishG 1 Reply Last reply
    0
  • girishG Offline
    girishG Offline
    girish Staff
    wrote on last edited by
    #2

    https://github.com/mattermost/mattermost/issues/18351 is tracking how to migrate.

    https://docs.mattermost.com/manage/bulk-export-tool.html and https://docs.mattermost.com/onboard/bulk-loading-data.html is possible the way to migrate but it says it doesn't migrate everything.

    1 Reply Last reply
    0
  • girishG Offline
    girishG Offline
    girish Staff
    replied to c0decafe on last edited by
    #3

    @c0decafe said in Mattermost v8.0+ and PostgreSQL:

    Any plans to migrate the cloudron mattermost app to PostgreSQL in the near future?

    yes, we will also move. Though the migration won't be automatic. I think we will just push a new package.

    C 1 Reply Last reply
    2
  • C Offline
    C Offline
    c0decafe
    replied to girish on last edited by
    #4

    @girish great, thank you. would be glad to help with testing or packaging.

    1 Reply Last reply
    0
  • M Offline
    M Offline
    mtd-sales
    wrote on last edited by
    #5

    I am running Cloudron for 10+ paying customers and counting. One of the reasons how I convince them to use Cloudron is the maintenance of their open source software. All of them use mostly Mattermost. Obviously I’m not too happy that you don’t offer a migration path and make us do the work manually.

    1 Reply Last reply
    0
  • girishG Offline
    girishG Offline
    girish Staff
    wrote on last edited by girish
    #6

    @mtd-sales you have to ask Mattermost team to provide a proper a migration path, this is not something we (cloudron team) can do. We just package the app.

    https://github.com/mattermost/mattermost/issues/18351 is the upstream issue.

    ericdrgnE 1 Reply Last reply
    1
  • M Offline
    M Offline
    mtd-sales
    wrote on last edited by
    #7

    @girish I understand, thank you. Looks like they are working on a migration path. So I would prefer to wait before packaging a new one.

    1 Reply Last reply
    1
  • ericdrgnE Offline
    ericdrgnE Offline
    ericdrgn
    wrote on last edited by
    #8

    @girish Don't know if this helps at all but someone added a great guide on the upstream issue. https://github.com/mattermost/mattermost/issues/18351#issuecomment-1682072226

    1 Reply Last reply
    1
  • ericdrgnE Offline
    ericdrgnE Offline
    ericdrgn
    replied to girish on last edited by
    #9

    @girish looks like that issue https://github.com/mattermost/mattermost/issues/18351 is officially closed as the migration path is documented and successful at this point.

    girishG 1 Reply Last reply
    1
  • girishG Offline
    girishG Offline
    girish Staff
    replied to ericdrgn on last edited by
    #10

    @ericdrgn thanks. https://github.com/mattermost/docs/blob/master/source/deploy/postgres-migration.rst are the instructions it seems.

    I am thinking of the below:

    • pgLoader, morph and dbcmp tools can be preinstalled into the package.
    • New installations will use postgres automatically
    • Existing package will be converted to contain access to both a postgres and mysql database. Users have to follow the upstream docs to migrate.

    Thoughts?

    1 Reply Last reply
    0
  • ericdrgnE Offline
    ericdrgnE Offline
    ericdrgn
    wrote on last edited by
    #11

    That's probably the best way to do it, if anyone doesn't necessarily care about the data in mattermost they can just archive the mysql version and spin up a new one that automatically uses postgres, otherwise the migration steps aren't crazy if maintaining the data is important.

    1 Reply Last reply
    0

  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks