feat(forgejo): global repository, upload, attachment and mirror limits #515
Inga granskare
Etiketter
Inga etiketter
area/backups
area/ci
area/control-panel
area/identity
area/infra
area/observability
area/payments
area/security
area/storage
area/web
blocked
needs-info
needs-triage
ready-for-implementation
type
bug
type
chore
type
docs
type
epic
type
feature
type
task
wontfix
Ingen milstolpe
Inget projekt
Inga tilldelade
1 deltagare
Notiser
Förfallodatum
Inget förfallodatum satt.
Beroenden
Inga beroenden satta
Referens
bitborg/bitborg-infra!515
Läser in…
Hänvisa till i nytt ärende
Ingen beskrivning angiven.
Ta bort grenen "feat/495-per-user-limits"
Borttagning av en gren är permanent. Även om den borttagna grenen kan fortsätta existera en kort tid innan den faktiskt tas bort, kan det INTE ångras i de flesta fall. Vill du fortsätta?
What
Global Forgejo limits in
app.ini, as role defaults inroles/forgejo/defaults/main.yml. Keys verified against the v16.0.5app.example.iniand the config cheat sheet.[repository] MAX_CREATION_LIMIT[repository.upload] FILE_MAX_SIZE/MAX_FILES[attachment] MAX_SIZE/MAX_FILES[mirror] MIN_INTERVAL/DEFAULT_INTERVALMAX_CREATION_LIMITis a fail-closed default. The reconciler setsmax_repo_creationper user on every run (10 for participants and exempt accounts, 100 for paid), which overrides it. The global value only applies to an account the reconciler has not reached yet, so it must not exceed the participant cap.Runbook: new "Per-user limits (#495)" section.
local/vars.local.ymlmirrors the values;make render-onlyrenders them.Not done
Apply
Forgejo role only.
app.inichanges, so Forgejo restarts once.Refs #495