Orgs, repo names and storage limits
Names
Every repo has an owner: a person or an org. Its full name is owner/repo, like GitHub.
- Your personal namespace is your username, made from your sign-in name (lowercase; letters, digits,
-,_,.). Existing users and repos from before orgs were added were moved under their creator (lead/game). lode workspace create --repo game --create-repocreates<you>/game.--repo studio/gamecreates it in the org.- When you name an existing repo without an owner, LodeBase uses the one repo by that name you can see. If there are several, it asks you to say which.
- Org names and usernames share one namespace, so an org can't take someone's username.
Orgs
sh
lode org create studio --display-name "Byrd Nest Studio" # you become its owner
lode org member studio user:alice # member (the default)
lode org member studio group:artists member # groups from authentik work too
lode org member studio user:bob owner
lode org remove studio user:alice
lode org set studio --member-role contributor --members-create-repos true
lode org show studio # members, repos, storage
lode org list # your orgs, and your own namespace's storage
lode org delete studio # only once it owns no reposRun these anywhere; outside a workspace, add --server if you're signed in to more than one server.
| Org role | On every repo of the org |
|---|---|
| owner | admin (and can change the org) |
| member | the org's member role: viewer, contributor (default) or maintainer |
Membership is managed in LodeBase. Per-repo grants (lode access grant) still work on top of the org role; the higher of the two wins. Org repos are private to the org: unlike personal repos, they don't get the server's LODEBASE_DEFAULT_ROLE for everyone. By default only owners create repos in an org; --members-create-repos true lets members too. If the server sets LODEBASE_REPO_CREATION=admins, only server admins create orgs and personal repos.
Renaming and moving
sh
lode repo info
lode repo rename studio/arena # rename, or move to another owner (needs admin on the repo
# and the right to create repos in the new owner)The old name becomes an alias: workspaces, scripts and old web links keep working, and the web app redirects to the new name. If a new repo later takes the old name, the alias goes away.
Storage limits
Storage counts each repo's content: every file version and its history, plus its pipeline artifacts, after deduplication within the repo. Logs aren't counted. Retention and garbage collection give space back (retention-and-gc.md).
Limits apply at two levels, and both must have room:
- Per repo: the repo's own limit, else its org's per-repo limit, else
LODEBASE_REPO_STORAGE_GB. - Per owner (all of an owner's repos together): the org's limit, else
LODEBASE_ORG_STORAGE_GB; for people,LODEBASE_USER_STORAGE_GB.
0 means no limit. Server admins (LODEBASE_ADMINS) change limits:
sh
lode org set studio --limit 2TB --repo-limit 500GB
lode org set studio --limit default # back to the server default
lode repo limit 750GB # this repo onlyA submit that would go over a limit is refused while it uploads, with a message saying which limit. Nothing lands; the uploaded objects are removed by garbage collection later. The web app shows usage on the repo list and on each org page (/o/<org>).