gitea

recipe-maintainers/gitea

Fork 0

Author	SHA1	Message	Date
autonomic-bot	d41452663f	fix(config): seed app.ini when missing OR empty (-s), bump v3 A release that mounted app.ini directly as a read-only swarm config leaves a 0-byte placeholder at /etc/gitea/app.ini in the reattached config volume on upgrade; the original seed guard (! -f) treated that as present and skipped, so Gitea booted the install wizard on an empty config (/api/v1/version 404). Guard on ! -s (missing OR empty) so the rendered config is seeded; bump DOCKER_SETUP_SH_VERSION so the corrected entrypoint deploys (immutable swarm configs).	2026-06-18 02:52:50 +00:00
autonomic-bot	1a098452f4	fix(config): make app.ini writable so Gitea can persist secrets on (re)deploy Gitea 1.24+ (re)generates and SAVES the [oauth2] JWT secret to /etc/gitea/app.ini at LoadCommonSettings. With app.ini mounted directly as a read-only swarm config this fails fatally (open /etc/gitea/app.ini: read-only file system) on a warm reattach/redeploy, crash-looping the container before any DB migration. Mount the rendered config at /etc/gitea/app.ini.init (read-only) and seed it once into the writable config volume via docker-setup.sh, so Gitea owns a writable /etc/gitea/app.ini. Bumps DOCKER_SETUP_SH_VERSION so the new entrypoint actually deploys.	2026-06-18 01:52:58 +00:00
notplants	ce4de9e645	Merge pull request 'feat: support Git LFS on plain gitea' (#57 ) from lfs into master Reviewed-on: https://git.coopcloud.tech/coop-cloud/gitea/pulls/57 Reviewed-by: ammaratef45 <ammaratef45@proton.me>	2026-06-15 21:08:52 +00:00

Author

SHA1

Message

Date

autonomic-bot

d41452663f

fix(config): seed app.ini when missing OR empty (-s), bump v3

A release that mounted app.ini directly as a read-only swarm config leaves a 0-byte placeholder at
/etc/gitea/app.ini in the reattached config volume on upgrade; the original seed guard (! -f) treated
that as present and skipped, so Gitea booted the install wizard on an empty config (/api/v1/version
404). Guard on ! -s (missing OR empty) so the rendered config is seeded; bump DOCKER_SETUP_SH_VERSION
so the corrected entrypoint deploys (immutable swarm configs).

2026-06-18 02:52:50 +00:00

autonomic-bot

1a098452f4

fix(config): make app.ini writable so Gitea can persist secrets on (re)deploy

Gitea 1.24+ (re)generates and SAVES the [oauth2] JWT secret to /etc/gitea/app.ini at
LoadCommonSettings. With app.ini mounted directly as a read-only swarm config this fails fatally
(open /etc/gitea/app.ini: read-only file system) on a warm reattach/redeploy, crash-looping the
container before any DB migration. Mount the rendered config at /etc/gitea/app.ini.init (read-only)
and seed it once into the writable config volume via docker-setup.sh, so Gitea owns a writable
/etc/gitea/app.ini. Bumps DOCKER_SETUP_SH_VERSION so the new entrypoint actually deploys.

2026-06-18 01:52:58 +00:00

notplants

ce4de9e645

Merge pull request 'feat: support Git LFS on plain gitea' (#57 ) from lfs into master

Reviewed-on: https://git.coopcloud.tech/coop-cloud/gitea/pulls/57
Reviewed-by: ammaratef45 <ammaratef45@proton.me>

2026-06-15 21:08:52 +00:00

Compare commits

Diff Content Not Available