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
mesh/check checking 4becc7bd8312 on 53d173aa7de5
mesh/delivery merged: source.main moved to novox/mesh-catalog@53d173aa7de5
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
This commit is contained in:
@@ -7,6 +7,6 @@ GITEA__database__PASSWD=${secret:postgres-database}
|
||||
GITEA__webhook__ALLOWED_HOST_LIST=172.17.0.1
|
||||
# Issue 1966: cap the forge's own pool; the store's 100 connections are shared by every module on this machine.
|
||||
# SSH git operations go through the forge's private API, so this pool carries them.
|
||||
GITEA__database__MAX_OPEN_CONNS=40
|
||||
GITEA__database__MAX_IDLE_CONNS=10
|
||||
GITEA__database__CONN_MAX_LIFETIME=5m
|
||||
GITEA__database__MAX_OPEN_CONNS=${config:database-max-open-connections}
|
||||
GITEA__database__MAX_IDLE_CONNS=${config:database-max-idle-connections}
|
||||
GITEA__database__CONN_MAX_LIFETIME=${config:database-connection-lifetime}
|
||||
|
||||
Reference in New Issue
Block a user