Commit b47ac9b55a
Verified · cmc
Layout: unified · split
Admin.org +10
| @@ -212,6 +212,16 @@ deploy, an archive publish, an automated MR branch — needs an explicit | ||
| 212 | 212 | grant on that repo: =repo access grant <owner/name> ci write=. Private |
| 213 | 213 | repos likewise need at least read for the clone. |
| 214 | 214 | |
| 215 | * LFS storage | |
| 216 | ||
| 217 | Objects live content-addressed under =[lfs] root= (default | |
| 218 | =<server.root>/lfs=); =[lfs] max_object_bytes= caps a single object | |
| 219 | (512MB default). Storage sits behind a small interface — an | |
| 220 | S3-compatible backend is a drop-in with the server proxying, and | |
| 221 | presigned URLs a later optimization. LFS objects do not travel with | |
| 222 | push mirrors (mirrors move git refs only), and gc does not yet collect | |
| 223 | orphaned objects. | |
| 224 | ||
| 215 | 225 | * Pages |
| 216 | 226 | |
| 217 | 227 | =[pages] domain = "example.site"= serves public repos' =pages= branches |
Users.org +9
| @@ -333,6 +333,15 @@ matching tag is pushed — and only then; =schedule= and =tags= are | ||
| 333 | 333 | mutually exclusive. =build trigger <owner/name> <job>= queues any job |
| 334 | 334 | immediately. |
| 335 | 335 | |
| 336 | * Large files (LFS) | |
| 337 | ||
| 338 | Standard Git LFS works over both transports with no setup beyond the | |
| 339 | usual =git lfs track=. SSH remotes authenticate through | |
| 340 | =git-lfs-authenticate= (deploy keys included: ro keys can download, rw | |
| 341 | keys upload); anonymous HTTPS clones of public repositories can fetch | |
| 342 | LFS objects with no credentials. Objects are verified against their | |
| 343 | sha256 on upload and capped at 512MB by default. | |
| 344 | ||
| 336 | 345 | * Pages |
| 337 | 346 | |
| 338 | 347 | On instances with =[pages] domain= set, a =pages= branch in any public |