You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- require Docker isolation for production pipeline commands
- add restricted CI networking and runtime health checks
- secure pipeline secrets, paths, artifacts, and cancellation
- add explicit per-repository Pages publishing controls
- preserve web, Pages, HTTP, and SSH access across repo renames
- fully clean repository data and unshared LFS objects on deletion
- restore queued runs and scope cancellation to individual runs
- fix pnpm 11.1.3 CI setup and documentation deep links
- add migrations, documentation, and regression coverage
|`DATA_DIR`|`./data`| Directory for database, repositories, and LFS objects |
116
-
|`EXTERNAL_URL`|`http://localhost:$PORT`| Public-facing URL (required for Git LFS over SSH) |
111
+
See the [configuration guide](packages/docs/src/pages/configuration.mdx) for the complete environment reference, including Docker runner limits and Pages settings.
Production CI requires a dedicated `groffee-ci` Docker network with restricted egress. See the configuration guide before enabling repository pipelines.
126
+
127
+
Pages publishing is disabled per repository by default, including for public repositories. An
128
+
owner must explicitly enable it in repository settings. Published Pages sites are public even when
0 commit comments