fix: remove /etc/timezone bind mount, not present on all hosts

Docker Swarm requires the bind source to exist on the node before scheduling the task; /etc/timezone is Debian/Ubuntu-specific and missing on other distros, causing deploy failures. /etc/localtime alone covers timezone info portably.
chore: publish 3.6.3+1.27.1-rootless release
2026-08-14 17:39:21 -04:00 · 2026-08-10 12:57:05 -04:00 · 2026-08-10 16:54:41 +00:00 · 2026-08-10 16:52:09 +00:00
2 changed files with 2 additions and 3 deletions
@@ -1,4 +1,4 @@
-export APP_INI_VERSION=v22
+export APP_INI_VERSION=v23
 export DOCKER_SETUP_SH_VERSION=v1
 export PG_BACKUP_VERSION=v1

@@ -56,7 +56,6 @@ services:
    volumes:
      - data:/var/lib/gitea
      - config:/etc/gitea
-      - /etc/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro
    networks:
      - proxy
@@ -87,7 +86,7 @@ services:
        - "traefik.http.middlewares.${STACK_NAME}_cors.headers.accesscontrolalloworiginlist=https://${GITEA_CORS_ALLOW_DOMAIN}"
        - "traefik.http.middlewares.${STACK_NAME}_cors.headers.accesscontrolmaxage=100"
        - "traefik.http.middlewares.${STACK_NAME}_cors.headers.addvaryheader=true"
-        - coop-cloud.${STACK_NAME}.version=3.6.2+1.27.1-rootless
+        - coop-cloud.${STACK_NAME}.version=3.6.3+1.27.1-rootless


 networks:
Author	SHA1	Message	Date
Beto	c52ccd5606	fix: remove /etc/timezone bind mount, not present on all hosts Docker Swarm requires the bind source to exist on the node before scheduling the task; /etc/timezone is Debian/Ubuntu-specific and missing on other distros, causing deploy failures. /etc/localtime alone covers timezone info portably.	2026-08-14 17:39:21 -04:00
notplants	97fe2bf213	chore: publish 3.6.3+1.27.1-rootless release	2026-08-10 12:57:05 -04:00
notplants	fe536b276b	Merge pull request 'fix: bump APP_INI_VERSION to v23' (#62 ) from fix-app-ini-version into master Reviewed-on: coop-cloud/gitea#62	2026-08-10 16:54:41 +00:00
autonomic-bot	852717d212	fix: bump APP_INI_VERSION to v23 app.ini.tmpl changed in "BREAKING CHANGE: remove forgejo" but the config version stayed at v22. Swarm configs are immutable, so upgrading an existing deployment aborts: FATA failed to update config <stack>_app_ini_v22: Error response from daemon: rpc error: code = InvalidArgument desc = only updates to Labels are allowed Bumping to v23 makes Swarm create a new config object instead of mutating v22; the orphaned v22 can be pruned after rollout.	2026-08-10 16:52:09 +00:00