Forge database pool caps are config values, and a changed value recreates the forge (issue 1966, recovery) #633

Merged

mesh-tools merged 1 commits from fix/1966-gitea-pool-config into main

2026-11-08 03:41:24 +00:00

Author	SHA1	Message	Date
jschoubben	4becc7bd83	Forge database pool caps are config values and a change recreates the forge (issue 1966, recovery) mesh/delivery merged: source.main moved to novox/mesh-catalog@53d173aa7de5 Details mesh/check checking 4becc7bd8312 on 53d173aa7de5 The caps were literals in server.env and the container named no restart-on, so a changed env-file never reached the running forge. They are now three gitea config values placed with ${config:...}, and the server container restarts on server-env. Claude-Session: https://claude.ai/code/session_01NcbgfFfQ4Z9UE5jK32PmE5	2026-11-08 03:33:16 +01:00

Author

SHA1

Message

Date

jschoubben

4becc7bd83

Forge database pool caps are config values and a change recreates the forge (issue 1966, recovery)

mesh/delivery merged: source.main moved to novox/mesh-catalog@53d173aa7de5

Details

mesh/check checking 4becc7bd8312 on 53d173aa7de5

The caps were literals in server.env and the container named no restart-on, so a changed env-file never reached the running forge. They are now three gitea config values placed with ${config:...}, and the server container restarts on server-env.

Claude-Session: https://claude.ai/code/session_01NcbgfFfQ4Z9UE5jK32PmE5

2026-11-08 03:33:16 +01:00