Add an opt-in compose.lfs.yml that mounts the lfs_jwt_secret secret and
enables GITEA_LFS_START_SERVER for use of lfs with plain gitea (previously lfs required forgejo)
Add an opt-in compose.lfs.yml that mounts the lfs_jwt_secret secret and
enables GITEA_LFS_START_SERVER for use of lfs with plain gitea (previously lfs required forgejo)
based on the thread and feature request here: https://matrix.to/#/!DfXPgKLoYCvjHithgS:autonomic.zone/$ZCyxEXNmFyUy420c9CFsbb-zxBb80i45L6Qu8bo0plc?via=autonomic.zone&via=matrix.org&via=pub.solar
Add an opt-in compose.lfs.yml that mounts the lfs_jwt_secret secret and
enables GITEA_LFS_START_SERVER for plain gitea (forgejo already bundles
LFS). Emit LFS_JWT_SECRET in app.ini whenever the LFS server is on so the
JWT secret is stable across redeploys instead of being regenerated on
every restart (app.ini is a read-only config mount).
Bump version 3.5.2 -> 3.6.0.
this is already deployed live to git.cooopcloud.tech and I tested it there (lfs seems to be working)
cc recent committers for review @p4u1 @fauno @ammaratef45 @3wordchant if anyone wants to take a look
ammaratef45
approved these changes 2026-06-15 20:03:03 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Add an opt-in compose.lfs.yml that mounts the lfs_jwt_secret secret and
enables GITEA_LFS_START_SERVER for use of lfs with plain gitea (previously lfs required forgejo)
based on the thread and feature request here: https://matrix.to/#/!DfXPgKLoYCvjHithgS:autonomic.zone/$ZCyxEXNmFyUy420c9CFsbb-zxBb80i45L6Qu8bo0plc?via=autonomic.zone&via=matrix.org&via=pub.solar
this is already deployed live to git.cooopcloud.tech and I tested it there (lfs seems to be working)
cc recent committers for review @p4u1 @fauno @ammaratef45 @3wordchant if anyone wants to take a look
lgtm!