coop-cloud/loomio
coop-cloud/loomio
1
0
Fork 0
Code Issues 3 Pull Requests 2 Projects Releases Wiki Activity

make channels container externally available #12

Merged
3wordchant merged 4 commits from fix-channels-container into main 2025-06-06 19:19:06 +00:00
Conversation 1 Commits 4 Files Changed 2 +19
2 changed files with 19 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
README.md
View File

@ -21,6 +21,7 @@
* `abra app deploy <app-name>`
* Open the configured domain in your browser to create your user account (only works in case mail is configured correctly)
* Give yourself admin rights by running `abra app cmd <app-name> app make_last_user_admin`
* Deploy [swarm-cronjob](https://recipes.coopcloud.tech/swarm-cronjob) on your server if it is not running yet. This is needed for loomios cron container to be started to do hourly chores.
## Migration guide

18
compose.yml
View File

@ -72,6 +72,12 @@ services:
- "traefik.http.routers.${STACK_NAME}.tls.certresolver=${LETS_ENCRYPT_ENV}"
- "coop-cloud.${STACK_NAME}.version=4.0.2+v2.25.4"
- "backupbot.backup:=${ENABLE_BACKUPS:-true}"
- "traefik.http.routers.${STACK_NAME}.middlewares=${STACK_NAME}"
- "traefik.http.middlewares.${STACK_NAME}.headers.accesscontrolallowmethods=GET,OPTIONS,PUT"
- "traefik.http.middlewares.${STACK_NAME}.headers.accesscontrolallowheaders=*"
- "traefik.http.middlewares.${STACK_NAME}.headers.accessControlAllowOriginList=https://*.${DOMAIN}"
3wordchant marked this conversation as resolved Outdated
3wordchant commented 2025-05-03 21:34:51 +00:00
Outdated
Review
Copy Link

Is this needed for all Loomio deployments, or just when accessing content from another service?

Is this needed for all Loomio deployments, or just when accessing content from another service?
stevensting commented 2025-05-04 11:23:38 +00:00
Outdated
Review
Copy Link

tbh, I did not quiet figure out what the impact was, I stumbled across this error message when searching for another issue. Maybe check your javascript console on your loomio instance if you experience the same thing.
(My issue was the cron container not running because we were missing the swarm-cronjob docker plugin.)

tbh, I did not quiet figure out what the impact was, I stumbled across this error message when searching for another issue. Maybe check your javascript console on your loomio instance if you experience the same thing. (My issue was the cron container not running because we were missing the swarm-cronjob docker plugin.)
stevensting commented 2025-05-04 11:50:40 +00:00
Outdated
Review
Copy Link

made one more small adaption to improve security

made one more small adaption to improve security
- "traefik.http.middlewares.${STACK_NAME}.headers.accesscontrolmaxage=100"
- "traefik.http.middlewares.${STACK_NAME}.headers.addvaryheader=true"
worker:
image: loomio/loomio:v2.25.4
configs:
@ -133,10 +139,22 @@ services:
image: loomio/loomio_channel_server
networks:
- backend
- proxy
depends_on:
- redis
environment:
<<: *redis-env
VIRTUAL_HOST: channels.${DOMAIN}
deploy:
labels:
- "traefik.enable=true"
- "traefik.docker.network=proxy"
- "traefik.http.routers.channels${STACK_NAME}.rule=Host(`channels.${DOMAIN}`)"
- "traefik.http.routers.channels${STACK_NAME}.tls=true"
- "traefik.http.routers.channels${STACK_NAME}.tls.certresolver=${LETS_ENCRYPT_ENV}"
- "traefik.http.services.channels${STACK_NAME}.loadbalancer.server.port=5000"
- "traefik.http.routers.channels${STACK_NAME}.entrypoints=web-secure"
cron:
image: loomio/loomio:v2.25.4
configs: