Storage
Where workspace files are kept in your R2, S3 or GCS buckets, which bucket new workspaces use, and how long deleted work is kept.
A workspace's files live on its runner. Yard also keeps a copy of them in an object storage bucket, so they survive a runner going away, can be read while the runner is offline, and can move to another runner.
Storage settings are for organization admins, under Settings, Storage & git.
Supported providers
- Cloudflare R2
- Amazon S3
- Google Cloud Storage (with HMAC keys)
- any S3-compatible service
Yard managed needs no setup of your own: Yard keeps the files in storage it provides. Buckets Yard provides appear in the lists marked as such.
Your organization's bucket
At the top of Settings, Storage & git, under Persistent storage, pick a provider and fill in the bucket, region, endpoint, access key id and secret access key. Choose Save, then Test connection: Yard writes a test object, reads it back and deletes it, and says which step failed if one does.
The secret key is sealed in your browser to your organization's vault: only its runners can open it, Yard's servers cannot. A runner of the organization signs every upload and download link, so one of them must be online for files to move. The key is never shown again; leave the field empty to keep the stored one. Use a key that can only read and write that one bucket.
The bucket also carries a project's source when you start its
apps on another runner than the workspace's own: a
packed copy of the worktree, under orgs/<org>/hosted/, replaced at each
start. Apps on the workspace's own runner need no bucket; without one, apps
on another runner cannot start yet.
Buckets
Below it, Buckets lists every bucket your workspaces can use. Choose Add bucket to add another, with a name people pick it by (for example "EU (Frankfurt)"), the provider and its credentials. For each of your organization's buckets you can:
- Make default: new workspaces go to this bucket.
- Stop new workspaces or Take new workspaces: whether the bucket is offered for new workspaces at all. Existing workspaces stay.
- Test the connection.
- Remove it. This is only possible when no workspace uses it. Yard forgets the bucket and its key; nothing in the bucket is deleted.
Buckets Yard provides are listed too, marked as such. They cannot be changed here.
Which bucket a workspace uses
When you create a workspace, it goes to the default bucket. If several buckets take new workspaces, the New workspace dialog lets you choose. A workspace then stays in that bucket: changing the default later does not move it.
To move a workspace, open Storage in the workspace settings under General, which names its bucket, and choose a bucket under Move them to. Yard copies the files, then switches over and keeps the old copy. A move takes a while, and uploads pause for about two minutes at the end. The progress shows in the same place; if a move fails, the files stay where they were.
Retention
Keep deleted projects and archived workspaces for sets how long their files stay in the bucket: 3, 7, 14, 30 or 90 days, 1 year, or forever. The runtime (containers, worktrees) is removed right away; only the stored files are kept.
Archived workspaces are listed under Archived on the organization's workspaces page. While they are kept, View opens a read-only copy of the workspace from storage, and workspace owners can Recover the workspace onto a runner or Delete it. Deleted projects are covered in projects and specs.
Workspace history
Pushing a workspace's history to a GitHub repository is not a storage setting. The repository is chosen per workspace in the workspace settings under General, History remote. See history.