[mass update] fix supporting multiple domains while enforcing ssl

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
@@ -24,33 +26,26 @@ steps:
         from_secret: autono_bot_access_token
     depends_on:
     - deployment
-  when:
-    status:
-      - failure
+    when:
+      status:
+        - failure
 trigger:
   branch:
     - main
 
 ---
 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
+        - toolshed/auto-recipes-catalogue-json
+
+trigger:
+  event: tag

.env.sample

@@ -1,4 +1,4 @@
-TYPE=mattermost
+TYPE=mattermost-lts
 
 # Domain of service
 DOMAIN=mattermost.example.com

README.md

@@ -2,14 +2,14 @@
 
 <!-- metadata -->
 
-* **Category**:
-* **Status**: 
-* **Image**:
-* **Healthcheck**: N
-* **Backups**: N
-* **Email**: 
-* **Tests**: N
-* **SSO**: N
+* **Category**: Apps
+* **Status**: 3
+* **Image**: [`mattermost/mattermost-team-edition`](https://hub.docker.com/r/mattermost/mattermost-team-edition), 4, upstream
+* **Healthcheck**: No
+* **Backups**: Yes
+* **Email**: 1
+* **Tests**: 2
+* **SSO**: No
 
 <!-- endmetadata -->
 

compose.yml

@@ -2,7 +2,7 @@ version: "3.8"
 
 services:
   app:
-    image: mattermost/mattermost-team-edition:8.0.1
+    image: mattermost/mattermost-team-edition:10.5.10
     environment:
       - TZ
       - MM_SQLSETTINGS_DRIVERNAME=postgres
@@ -26,9 +26,11 @@ services:
         - "traefik.http.routers.${STACK_NAME}.tls.certresolver=${LETS_ENCRYPT_ENV}"
         - "traefik.http.routers.${STACK_NAME}.entrypoints=web-secure"
         - "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.1.0+8.0.1"
+        - "traefik.http.middlewares.${STACK_NAME}-redirect.redirectscheme.scheme=https"
+        - "traefik.http.middlewares.${STACK_NAME}-redirect.redirectscheme.permanent=true"
+        - "coop-cloud.${STACK_NAME}.version=2.0.4+10.5.10"
+        - "backupbot.backup=true"
+        - "backupbot.backup.path=/mattermost,/etc/ssl"
     configs:
       - source: abra_mattermost_entrypoint
         target: /abra-mattermost-entrypoint.sh
@@ -50,6 +52,12 @@ services:
       - 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:

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.

release/1.4.1+9.5.11

@@ -0,0 +1 @@
+hotfix: rollback to last functional version

release/2.0.2+10.5.8

@@ -0,0 +1 @@
+Mattermost Platform Extended Support Release 10.5.8 contains a high severity level security fix.