Mattermost 9.11

[hnykda]

I managed to run Mattermost, here is the config as Docker Compose type of deployment:

services:
  postgres:
    image: 'postgres:${POSTGRES_IMAGE_TAG}'
    restart: '${RESTART_POLICY}'
    security_opt:
      - 'no-new-privileges:true'
    pids_limit: 100
    read_only: true
    tmpfs:
      - /tmp
      - /var/run/postgresql
    volumes:
      - '${POSTGRES_DATA_PATH}:/var/lib/postgresql/data'
    environment:
      - TZ
      - POSTGRES_USER
      - POSTGRES_PASSWORD
      - POSTGRES_DB
  mattermost:
    depends_on:
      - postgres
    image: 'mattermost/${MATTERMOST_IMAGE}:${MATTERMOST_IMAGE_TAG}'
    restart: '${RESTART_POLICY}'
    security_opt:
      - 'no-new-privileges:true'
    pids_limit: 200
    read_only: '${MATTERMOST_CONTAINER_READONLY}'
    tmpfs:
      - /tmp
    volumes:
      - './config:/mattermost/config:rw'
      - './data:/mattermost/data:rw'
      - './logs:/mattermost/logs:rw'
      - './plugins:/mattermost/plugins:rw'
      - './client/plugins:/mattermost/client/plugins:rw'
      - './bleve-indexes:/mattermost/bleve-indexes:rw'
    environment:
      - TZ
      - MM_SQLSETTINGS_DRIVERNAME
      - MM_SQLSETTINGS_DATASOURCE
      - MM_BLEVESETTINGS_INDEXDIR
      - MM_SERVICESETTINGS_SITEURL
    expose:
      - 8065

Env file:

DOMAIN=<you-domain>
MATTERMOST_CONTAINER_READONLY=false
MATTERMOST_IMAGE=mattermost-enterprise-edition
MATTERMOST_IMAGE_TAG=9.11
MM_BLEVESETTINGS_INDEXDIR=/mattermost/bleve-indexes
# probably not needed
MM_SERVICESETTINGS_SITEURL=https://<your-domain>
MM_SQLSETTINGS_DATASOURCE=postgres://${POSTGRES_USER}:${POSTGRES_PASSWORD}@postgres:5432/${POSTGRES_DB}?sslmode=disable&connect_timeout=10
MM_SQLSETTINGS_DRIVERNAME=postgres
POSTGRES_DATA_PATH=./volumes/db/var/lib/postgresql/data
POSTGRES_DB=mattermost
POSTGRES_IMAGE_TAG=13-alpine
POSTGRES_PASSWORD=mmuser_password
POSTGRES_USER=mmuser
RESTART_POLICY=unless-stopped
TZ=Europe/Prague

After saving the file, I had to go to the coolify directory of the service, e.g. /data/coolify/services/isgow40goosk0osksc8wco8s on my server, and run:

sudo chown -R 2000:2000 bleve-indexes/ client/ config/ data/ logs plugins

then, after setting my domain (including https! - https://<my-domain>) in Domains under the mattermost service, it works.

More detailed guide below. I also used Mattermost official docker docs:

You don't need nginx and certificates from that guide, you are going to use Coolify's traefik automagic instead.

If you want push notifications on mobile devices, you also want to allow TPNS in mattermost admin console:

Optional

For backups, I have in my docker-compose file this service:

  dbbackups:
    image: 'kartoza/pg-backup:15-3.3'
    volumes:
      - './db-backups:/backups'
    environment:
      - POSTGRES_HOST=postgres
      - POSTGRES_USER=mmuser
      - POSTGRES_PASS=mmuser_password
      - REMOVE_BEFORE=7
      - DUMPPREFIX=mattermost
    restart: on-failure
    depends_on:
      postgres:
        condition: service_healthy

which makes daily dumps in that data folder (which I backup regularly).

[MaxAryus]

I get the following error when starting the service…

Starting containers.
time="2024-08-29T17:21:11Z" level=warning msg="The "POSTGRES_USER" variable is not set. Defaulting to a blank string."
time="2024-08-29T17:21:11Z" level=warning msg="The "POSTGRES_PASSWORD" variable is not set. Defaulting to a blank string."
time="2024-08-29T17:21:11Z" level=warning msg="The "POSTGRES_DB" variable is not set. Defaulting to a blank string."

Edit:

I guess the issue comes form the Mattermost container. In the logs it says:

Error: failed to load configuration: could not create config file: open /mattermost/config/config.json: permission denied

[hnykda]

Eh, I think I saw that too, but it's working nevertheless. You can try to hardcode them in the docker-compose directly.

[MaxAryus]

I did so but then the Error: Error: failed to load configuration: could not create config file: open /mattermost/config/config.json: permission denied shows up.

I tried opening the url but it says 404 page not found

[MaxAryus]

In generell. I experienced that all .env values are not working I needed to add them directly to the docker compose file.

[hnykda]

OK, weird, I didn't have that issue. Did you run that chown command?

[RowanAldean]

Can someone just give me a ELI5 step-by-step for getting this sorted on my Hetzner VPS? First time using Coolify

[hnykda]

Well, what have you tried so far? If your coolify setup works (e.g. domain etc.), you should be fine to:

1. go to projects -> resources -> select/create new project -> click New under resources
2. when creating new resource, click on Docker Compose under "Docker based"
3. into the "Docker Compose" text area that is on the screen insert the docker-compose I shared above
4. set domain, click save
   
5. set env vars from above (click developer view), then click save
   
6. you shouldn't IMHO need to set up volumes as they should get fetched from the docker-compose, but the page should look like this:
   
7. then you have to do the slightly weird task. You have to ssh to your VPS, and as a root go to the data directory of this service. For me, it was /data/coolify/services/isgow40goosk0osksc8wco8s (it's the same ID that is in the URL when setting this up), and run that sudo chown -R 2000:2000 bleve-indexes/ client/ config/ data/ logs plugins. I found out that this step is needed in in the Mattermost docker deployment use.
8. then go to coolify and click Deploy button

[RowanAldean]

Can't reach mattermost via 8065. Github didn't refresh so only just seeing this comment now when I refreshed my page!

Going to continue troubleshooting. Doesn't help that my domain DNS just points to the VPS. I don't know if I can subdomain at random like that :) i.e i'd need an A record for mattermost.<domain>.com

edit: bruh, just reading your reply about adding the domain via the UI. Trying this now.

[RowanAldean]

Got this functional but having trouble with TLS (using 443) for Mattermost. Anyone got any ideas?

[RowanAldean]

Ok, the last line you've added explains this - I don't need to worry as using Coolify Traefik magic. Going to assume that gives me encrypted comms (I suspected out-of-the-box was sufficient).

[hnykda]

Yeah, exactly. Don't ask me how it works, I just pointed *.mydomain to my VPS and let coolify traefik magic do it's thing.

[RowanAldean]

I'm doubtful on this actually being encyrpted 😂 I did setup the certs and CORS stuff though so now browser seems happy and things are functional. Just gotta move over our small team now!

[hnykda]

I am pretty confident it is getting encrypted, actually, thanks to letsencrytp and traefik etc. 😄 Good luck!

[RowanAldean]

Getting the github bot working with this stuff is ridiculous. Wasted so many hours with this today that i'm wondering if Coolify was even "cool".

Ridiculously overcomplicated. Getting 307s following docs or "Text not defined" if trying to just use Incoming Webhooks

[Blochergroup]

Nice tutorial:

For me it was applications instead of services.

Unfortunately somehow the env files won't work. I get this when starting it:
time="2024-09-06T21:06:50+02:00" level=warning msg="The "POSTGRES_USER" variable is not set. Defaulting to a blank string."

[peaklabs-dev]

Please make sure you are updated to the latest version, as there was a fix for "POSTGRES_USER" in it (just add the compose file again).

[Blochergroup]

@peaklabs-dev coolify is one v4.0.0-beta.330.

Still not working. Wonder if its related to the fact, that the volumes are in "applications" instead of services.

time="2024-09-07T13:50:38+02:00" level=warning msg="The \"POSTGRES_USER\" variable is not set. Defaulting to a blank string." time="2024-09-07T13:50:38+02:00" level=warning msg="The \"POSTGRES_DB\" variable is not set. Defaulting to a blank string."

[peaklabs-dev]

Could you please open a detailed issue with reproduction steps. Thanks.

[PsychoDude]

I had the exact same issue, got the latest version to work (10.0.0) thanks to Darren on discord. You are indeed correct, I had to chown the folders inside applications also. This is the Compose to get you up and running:

services:
  postgres:
    image: 'postgres:16-alpine'
    restart: unless-stopped
    security_opt:
      - 'no-new-privileges:true'
    pids_limit: 100
    read_only: true
    tmpfs:
      - /tmp
      - /var/run/postgresql
    volumes:
      - 'postgres:/var/lib/postgresql/data'
    environment:
      - TZ=UTC
      - 'POSTGRES_USER=${SERVICE_USER_POSTGRES:-postgres}'
      - 'POSTGRES_PASSWORD=${SERVICE_PASSWORD_POSTGRES}'
      - 'POSTGRES_DB=${DB_POSTGRES:-postgres}'
  mattermost:
    depends_on:
      - postgres
    image: 'mattermost/mattermost-enterprise-edition:10.0.0'
    restart: unless-stopped
    security_opt:
      - 'no-new-privileges:true'
    pids_limit: 200
    read_only: false
    tmpfs:
      - /tmp
    volumes:
      - './config:/mattermost/config:rw'
      - './data:/mattermost/data:rw'
      - './logs:/mattermost/logs:rw'
      - './plugins:/mattermost/plugins:rw'
      - './client/plugins:/mattermost/client/plugins:rw'
      - './bleve-indexes:/mattermost/bleve-indexes:rw'
    environment:
      - SERVICE_FQDN_MATTERMOST_8065
      - TZ=UTC
      - MM_SQLSETTINGS_DRIVERNAME=postgres
      - 'MM_SQLSETTINGS_DATASOURCE=postgres://${SERVICE_USER_POSTGRES}:${SERVICE_PASSWORD_POSTGRES}@postgres:5432/${DB_POSTGRES:-postgres}?sslmode=disable&connect_timeout=10'
      - MM_BLEVESETTINGS_INDEXDIR=/mattermost/bleve-indexes
      - 'MM_SERVICESETTINGS_SITEURL=${SERVICE_FQDN_MATTERMOST}'
    expose:
      - 8065

No need to generate any env variables, they get auto-generated. It assigns a wildcard url if you have one set up for your server.

Note that the mattermost container does take a few minutes to boot up.

• You need to start a fresh service for this to work