chore: publish 0.3.2+8.1.7 release

Re: coop-cloud/recipes-catalogue-json#4

.drone.yml

@@ -3,10 +3,12 @@ kind: pipeline
 name: deploy to swarm-test.autonomic.zone
 steps:
   - name: deployment
-    image: decentral1se/stack-ssh-deploy:latest
+    image: git.coopcloud.tech/coop-cloud/stack-ssh-deploy:latest
     settings:
       host: swarm-test.autonomic.zone
       stack: mattermost
+      networks:
+       - proxy
       purge: true
       deploy_key:
         from_secret: drone_ssh_swarm_test
@@ -33,24 +35,17 @@ trigger:
 
 ---
 kind: pipeline
-name: recipe release
+name: generate recipe catalogue
 steps:
   - name: release a new version
-    image: decentral1se/drone-abra:latest
-    settings:
-      command: recipe mattermost release
-      deploy_key:
-        from_secret: abra_bot_deploy_key
-
-  - name: trigger downstream builds
     image: plugins/downstream
     settings:
-      server: https://drone.autonomic.zone
+      server: https://build.coopcloud.tech
       token:
-        from_secret: decentral1se_token
+        from_secret: drone_abra-bot_token
       fork: true
       repositories:
-        - coop-cloud/auto-apps-json
-    depends_on:
-      - release a new version
-on
+        - coop-cloud/auto-recipes-catalogue-json
+
+trigger:
+  event: tag

.env.sample

@@ -14,15 +14,3 @@ SECRET_POSTGRES_PASSWORD_VERSION=v1
 ## A list of these tz database names can be looked up at Wikipedia
 ## https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
 TZ=UTC
-
-## Make Mattermost container readonly. This interferes with the regeneration of root.html inside the container. Only use
-## it if you know what you're doing.
-## See https://github.com/mattermost/docker/issues/18
-MATTERMOST_CONTAINER_READONLY=false
-
-## Additional configuration settings for Mattermost. Documentation on the variables and the settings itself can be found at
-## https://docs.mattermost.com/administration/config-settings.html
-## Keep in mind that variables set here will take precedence over the same setting in config.json. This includes
-## the system console as well and settings set with env variables will be greyed out.
-
-

abra.sh

@@ -0,0 +1 @@
+export ENTRYPOINT_VERSION=v1

compose.yml

@@ -1,50 +1,19 @@
 version: "3.8"
 
 services:
-  postgres:
-    image: postgres:13-alpine
-    security_opt:
-      - no-new-privileges:true
-    tmpfs:
-      - /tmp
-      - /var/run/postgresql
-    volumes:
-      - postgres_data:/var/lib/postgresql/data
-    environment:
-      # timezone inside container
-      - TZ
-
-      # necessary Postgres options/variables
-      - POSTGRES_USER=mattermost
-      - POSTGRES_PASSWORD_FILE=/run/secrets/postgres_password
-      - POSTGRES_DB=mattermost
-    secrets:
-      - postgres_password
-    networks:
-      - internal
-
   app:
-    image: mattermost/mattermost-team-edition:5.39
-    security_opt:
-      - no-new-privileges:true
-    read_only: ${MATTERMOST_CONTAINER_READONLY}
-    tmpfs:
-      - /tmp
+    image: mattermost/mattermost-team-edition:8.1.7
+    environment:
+      - TZ
+      - MM_SQLSETTINGS_DRIVERNAME=postgres
+      - MM_SERVICESETTINGS_SITEURL=https://${DOMAIN}
     volumes:
       - mattermost_config:/mattermost/config:rw
       - mattermost_data:/mattermost/data:rw
       - mattermost_logs:/mattermost/logs:rw
       - mattermost_plugins:/mattermost/plugins:rw
       - mattermost_client_plugins:/mattermost/client/plugins:rw
-    environment:
-      # timezone inside container
-      - TZ
-
-      # necessary Mattermost options/variables (see env.sample)
-      - MM_SQLSETTINGS_DRIVERNAME=postgres
-
-      # additional settings
-      - MM_SERVICESETTINGS_SITEURL=https://${DOMAIN}
+      - mattermost_certs:/etc/ssl/certs:ro
     networks:
       - proxy
       - internal
@@ -59,6 +28,9 @@ services:
         - "traefik.http.routers.${STACK_NAME}.middlewares=${STACK_NAME}-redirect"
         - "traefik.http.middlewares.${STACK_NAME}-redirect.headers.SSLForceHost=true"
         - "traefik.http.middlewares.${STACK_NAME}-redirect.headers.SSLHost=${DOMAIN}"
+        - "coop-cloud.${STACK_NAME}.version=0.3.2+8.1.7"
+        - "backupbot.backup=true"
+        - "backupbot.backup.path=/mattermost,/etc/ssl"
     configs:
       - source: abra_mattermost_entrypoint
         target: /abra-mattermost-entrypoint.sh
@@ -67,6 +39,27 @@ services:
       - postgres_password
     entrypoint: /abra-mattermost-entrypoint.sh
 
+  postgres:
+    image: postgres:15-alpine
+    volumes:
+      - postgres_data:/var/lib/postgresql/data
+    environment:
+      - TZ
+      - POSTGRES_USER=mattermost
+      - POSTGRES_PASSWORD_FILE=/run/secrets/postgres_password
+      - POSTGRES_DB=mattermost
+    secrets:
+      - postgres_password
+    networks:
+      - internal
+    deploy:
+      labels:
+        backupbot.backup: "true"
+        backupbot.backup.pre-hook: "PGPASSWORD=$$(cat $${POSTGRES_PASSWORD_FILE}) pg_dump -U $${POSTGRES_USER} $${POSTGRES_DB} > /var/lib/postgresql/data/postgres-backup.sql"
+        backupbot.backup.post-hook: "rm -rf /var/lib/postgresql/data/postgres-backup.sql"
+        backupbot.backup.path: "/var/lib/postgresql/data/"
+
+
 secrets:
   postgres_password:
     external: true
@@ -74,8 +67,8 @@ secrets:
 
 configs:
   abra_mattermost_entrypoint:
-    name: abra_mattermost_entrypoint
-    file: ./abra-mattermost-entrypoint.sh
+    name: ${STACK_NAME}_entrypoint_${ENTRYPOINT_VERSION}
+    file: ./entrypoint.sh
 
 networks:
   proxy:
@@ -85,8 +78,8 @@ networks:
 volumes:
   postgres_data:
   mattermost_config:
+  mattermost_certs:
   mattermost_data:
   mattermost_logs:
   mattermost_plugins:
   mattermost_client_plugins:
-

release/0.1.0+7.0.txt

@@ -0,0 +1,6 @@
+This should be a fairly stable update. The only strange behaviour we've noticed so far has been:
+
+- When clicking on 'Channels' to change to 'Boards' or 'Playbooks', your window may flicker and just reload 'Channels'. Click 'Boards' or 'Playbooks' again and it should behave as expected.
+- When clicking on private messages, you may get an error telling you that you don't have permission to view these.
+
+To fix both of these errors, logout of your server in your Mattermost client, delete the server (if you are using an app), and then re-add it. We haven't noticed any issues after doing this.