coop-cloud/gitea
4
2
Fork 6
Code Issues 7 Pull Requests 4 Releases Wiki Activity

change deploy logic to stop-first instead of start-first #53

Merged
notplants merged 3 commits from stop-first into master 2026-06-04 16:47:01 +00:00
Conversation 4 Commits 3 Files Changed 1 +2 -2
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
compose.yml
View File

@ -71,7 +71,7 @@ services:
deploy:
update_config:
failure_action: rollback
order: start-first
order: stop-first
labels:
- "backupbot.backup=${ENABLE_BACKUPS:-true}"
- "traefik.enable=true"
@ -88,7 +88,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"
fauno commented 2026-05-28 20:47:23 +00:00
Outdated
Review
Copy Link

i don't think you need to bump the version on the pr itself, because this will be done by the abra recipe upgrade gitea step, and it will complain there's nothing to do

i don't think you need to bump the version on the pr itself, because this will be done by the `abra recipe upgrade gitea` step, and it will complain there's nothing to do
notplants commented 2026-06-04 16:46:14 +00:00
Outdated
Review
Copy Link

@fauna for some reason I have been in a habit of making the git tags manually instead of using abra recipe upgrade but maybe i should start using the actual tool (i think makes same result in the end though)

@fauna for some reason I have been in a habit of making the git tags manually instead of using `abra recipe upgrade` but maybe i should start using the actual tool (i think makes same result in the end though)
- coop-cloud.${STACK_NAME}.version=3.5.2+1.24.2-rootless
- coop-cloud.${STACK_NAME}.version=3.5.3+1.24.2-rootless
networks: