Browse Source

new: [mattermost] charm handles itself the websocket when in relation with apache

framadate
Valentin Lab 6 years ago
parent
commit
8232811276
  1. 32
      mattermost/metadata.yml

32
mattermost/metadata.yml

@ -1,5 +1,5 @@
# description: "Mattermost"
# maintainer: "Valentin Lab <valentin.lab@kalysto.org>"
description: "Mattermost"
maintainer: "Valentin Lab <valentin.lab@kalysto.org>"
## We fix image here to be sure of what we install ## We fix image here to be sure of what we install
docker-image: docker.0k.io/mattermost-team docker-image: docker.0k.io/mattermost-team
# docker-image: docker.0k.io/mattermost-enterprise # docker-image: docker.0k.io/mattermost-enterprise
@ -14,3 +14,31 @@ host-resources:
docker-compose: docker-compose:
restart: unless-stopped restart: unless-stopped
uses:
postgres-database:
constraint: required
auto: pair
solves:
database: "main storage"
log-rotate:
constraint: recommended
auto: pair
solves:
disk-leak: "/mattermost/logs"
web-proxy:
constraint: recommended
auto: pair
solves:
proxy: "Public access"
default-options:
apache-custom-rules:
- !var-expand |
ProxyPreserveHost On
# Set web sockets
RewriteEngine On
RewriteCond %{REQUEST_URI} /api/v[0-9]+/(users/)?websocket [NC,OR]
RewriteCond %{HTTP:UPGRADE} ^WebSocket$ [NC,OR]
RewriteCond %{HTTP:CONNECTION} ^Upgrade$ [NC]
RewriteRule .* ws://${MASTER_BASE_SERVICE_NAME}:8000%{REQUEST_URI} [P,QSA,L]
Loading…
Cancel
Save