Compare commits
1
Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
839ad23415 |
@@ -29,7 +29,7 @@ services:
|
||||
mode: 0600
|
||||
|
||||
searchindexer:
|
||||
image: nextcloud:32-fpm
|
||||
image: nextcloud:32.0.13-fpm
|
||||
volumes:
|
||||
- nextcloud:/var/www/html/
|
||||
- nextapps:/var/www/html/custom_apps:cached
|
||||
|
||||
@@ -11,8 +11,7 @@ services:
|
||||
|
||||
db:
|
||||
image: "pgautoupgrade/pgautoupgrade:14-debian"
|
||||
#setting max_connections with -c breaks pgautoupgrade
|
||||
#command: -c "max_connections=${MAX_DB_CONNECTIONS:-100}"
|
||||
command: -c "max_connections=${MAX_DB_CONNECTIONS:-100}"
|
||||
volumes:
|
||||
- "postgres:/var/lib/postgresql/data"
|
||||
networks:
|
||||
|
||||
+4
-4
@@ -48,7 +48,7 @@ services:
|
||||
start_period: 5m
|
||||
|
||||
app:
|
||||
image: nextcloud:32-fpm
|
||||
image: nextcloud:32.0.13-fpm
|
||||
depends_on:
|
||||
- db
|
||||
configs:
|
||||
@@ -95,7 +95,7 @@ services:
|
||||
failure_action: rollback
|
||||
order: start-first
|
||||
labels:
|
||||
- "coop-cloud.${STACK_NAME}.version=13.1.5+32.0.13-fpm"
|
||||
- "coop-cloud.${STACK_NAME}.version=13.1.1+32.0.12-fpm"
|
||||
- "coop-cloud.${STACK_NAME}.timeout=${TIMEOUT}"
|
||||
- "backupbot.backup=${ENABLE_BACKUPS:-true}"
|
||||
- "backupbot.backup.volumes.redis=false"
|
||||
@@ -109,7 +109,7 @@ services:
|
||||
start_period: 15m
|
||||
|
||||
cron:
|
||||
image: nextcloud:32-fpm
|
||||
image: nextcloud:32.0.13-fpm
|
||||
volumes:
|
||||
- nextcloud:/var/www/html/
|
||||
- nextapps:/var/www/html/custom_apps:cached
|
||||
@@ -125,7 +125,7 @@ services:
|
||||
|
||||
|
||||
cache:
|
||||
image: redis:8.8.1-alpine
|
||||
image: redis:8.10.0-alpine
|
||||
networks:
|
||||
- internal
|
||||
volumes:
|
||||
|
||||
@@ -1,2 +0,0 @@
|
||||
Important:
|
||||
The pgautoupgrade switch from 13.1.0+32.0.11-fpm was released untested and had a bug: the db service's `-c max_connections=...` command breaks pgautoupgrade, failing with `initdb: invalid option -- 'c'`. If your db got stuck mid-upgrade on 13.1.0-13.1.4 with that error: restore the old data dir and remove the upgrade lock file. Then redeploy this version.
|
||||
@@ -1 +0,0 @@
|
||||
Last release for nextcloud-32, pointing to the latest version of nextcloud-32.
|
||||
Reference in New Issue
Block a user