Repository navigation
feat: manual project backups (files and volumes in one snapshot) - #4894
neurekadev wants to merge 40 commits into
Conversation
…ping Scheduled system backups and system-managed volume backups share one admission and both default to 03:00. The one that started second was skipped, and the Activity Center reported the skip as a success. Scheduled runs now wait for the admission, up to six hours, and fail visibly if it never frees. Manual runs still return a conflict right away. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ention Scheduled runs now take the admission before reading their policy, so a policy edited or disabled during the wait is respected. Retention and runs resumed after a restart wait for the admission too. Before this, retention failed and marked a successful backup as failed whenever the other scheduled job grabbed the admission first, and a resumed backup could lose the admission to a redelivered waiting job. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…starts A manual system-managed volume backup started while another backup runs returns not-found or validation errors again instead of the conflict. Scheduled runs already hold the admission before calling prepare. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Manual system and volume backup workflows run one task at a time, and a new manual start parks the admission for its queued task. A resumed manual run that waited for the admission would block on that task until the six-hour timeout, so manual resumes fail fast again. Scheduled policy workflows never park the admission, so their resumes still wait. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A scheduled backup of a volume that another backup holds was skipped and reported as succeeded, and a scheduled system-managed run only counted that volume as skipped. Scheduled backups now wait for the volume's admission. Manual backups still fail fast, because a manual start parks the admission for its queued task. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…olume Scheduled per-volume and system-managed backups now take the volume admission before resolving their plan, so a policy edited, disabled, or deleted during the wait is respected. A per-volume policy disabled or deleted meanwhile ends its run as canceled, and a volume-level policy enabled meanwhile takes the volume out of the system-managed run. Manual starts keep their validation, authorization, then conflict order. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Project export can now include the project's named volumes in one portable bundle: a gzip tar with an arcane-project.json manifest, the existing project archive, and one existing volume archive per Compose key. The project can be stopped during export for a consistent copy. Import detects a bundle, refuses before changing anything if a target volume already exists, recreates the project and its volumes by Compose key, rolls back on a failed volume restore, and can start the project. Plain exports and plain project archives behave as before. The volume classification shared with project transfer moves to pkg/projects, so transfer, export, and the planned project backups use one rule. The UI gets Export on the project page and Import on the projects list; the CLI gets `projects export` and `projects import`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The export preview marks named volumes that don't exist yet as missing, so default exports of undeployed projects no longer fail. An explicitly requested missing volume is rejected before the project is stopped. Exports are written straight into their upload session instead of a temp file that was then copied, so they need one copy of disk space. Browsers download them through a new streaming upload-session download route instead of holding the whole bundle in memory; the session is removed once it is fully sent. Proxied upload chunk reads and downloads now check the upload kind's permission, so remote exports work for non-admin users. The CLI refuses a plain archive from a server that ignores the volume request. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
An empty named volume exports as an archive with only its root directory. The volume restore rejects empty uploads, so importing such a bundle failed and rolled the whole project back. Import now recognizes an empty volume archive and creates the Compose-labelled volume directly, tracked for rollback like restored volumes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
getarcaneapp#4876 merged as 40e65a7. Resolved the conflict by keeping upstream's removal of the admissionWait comment. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings in upstream main through getarcaneapp#4879. Resolved the en.json conflict by keeping upstream's new keys, then this branch's keys appended after them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Import was a menu action, which folded Update Projects into an Actions menu with it and broke the E2E tests that click Update Projects. Import is now a secondary button, so the projects header keeps its existing buttons. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A project backup is one Rustic snapshot of the project directory, the data of its selected volumes, and an arcane-project.json manifest, so files and volumes come from the same point in time. Containers are stopped for consistency by default and always started again; a resumed run restarts them first. Backups go to the shared volumes repository, where they deduplicate against volume backups, locally, to S3, or both. The project page gets a Backups tab to create, list, and delete them, behind a new projects:backup permission (granted by migration 118 where volumes:backup and projects:read are already held). The volumes repository, password resolution, container stop/start for backups, and source mount resolution move into internal/backup so volume, system, and project backups share them, without behaviour changes. Volume discovery skips project snapshots. Refs getarcaneapp#4880 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Back up now button sat in the table toolbar, which the backups table hides, so backups could not be started from the UI; it now sits next to the panel's description. S3 destinations referenced by project backups can no longer be deleted or moved. A delete that only removes the local snapshot updates the destination shown. Create and delete use the shared API result handling, and a failure to load S3 destinations is shown. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…d import Import checks the volume names the imported project actually uses before restoring anything, and only rolls back volumes it created, so a volume that existed before can no longer be deleted. Empty volumes keep the archive root's owner and mode. Export with stop only stops the project's running containers, holds the project lock while volumes are copied, and starts exactly those containers again instead of redeploying the whole project. The CLI downloads into a temporary file and only replaces the output once the download completes, so a failed re-export keeps the previous bundle; pipes such as /dev/stdout are still written directly. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
External volumes on the local driver without driver options are often just a way to pick the Docker volume name, so they are now included in exports by default like named volumes. Import recreates them under their exact name without Compose labels, or keeps an existing one as Compose would, never restoring into or deleting it. Volumes with driver options stay excluded. An export is no longer marked consistent when another project's running containers use one of its volumes, and the dialog says so. Rollback only removes volumes this import reports it created, and two volumes that resolve to the same Docker name are rejected before anything changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings in the export/import review fixes and local external volume support. Project backups now use the same rule: existing named volumes and local external volumes are captured, and volumes with driver options are left out. Resolved the en.json conflict by keeping both sets of keys. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
An import whose external volume already exists is now refused before anything changes, like named volumes, instead of reusing the existing volume. Imports are all or nothing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A consistent export now also stops containers Docker is restarting, so none can write while volumes are copied. Afterwards the stopped services are started through Compose, which honours depends_on and health conditions; containers Compose can't start on their own are started directly, and everything is started directly if Compose fails. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Compose keys that resolve to the same Docker volume now share one archive in the bundle, and import restores that volume once, so bundles where two external keys use the same name import again. External volumes keep their own Docker labels: export records them and import recreates the volume with them, still without Compose labels. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings in getarcaneapp#4887. Resolved the restore conflict by keeping its archive root owner and mode handling together with this branch's created reporting. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings in the export restart fixes, shared volume archives, external volume labels, and upstream main through getarcaneapp#4887. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ports clean An import now holds the project lock from before the project exists until its volumes are restored, it is started, or it is rolled back, so nothing can deploy it mid-restore. A bundle's recorded compose files are applied to the imported project's .env when the target would pick others, and the import is refused before anything is created if they can't be. The CLI prints nothing after an export written to stdout or another pipe. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Exporting the Compose project Arcane runs in with stop enabled would stop Arcane itself and leave it down. Arcane's containers are now skipped and count as in use, so such an export is not marked consistent. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Project backups now stop only the project's running and restarting containers, leave paused ones and other projects alone, and start them again through Compose so depends_on and health conditions hold. A backup is not marked consistent when another project's running container uses one of its volumes. The backup dialog offers the volumes the backend includes, local external volumes too, and warns about shared ones. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ning The in-use check counts every running container that the export does not stop, including standalone containers, not only other projects. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Resolves the in-use wording conflicts and applies the same wording to the backup dialog, the stopContainers doc, and the backup comments: anything outside the project keeps running, not only other projects. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A deploy, down, or project edit during a backup could fail against the stopped containers, change what the snapshot captures, or leave the restart to start containers without their Compose order. The backup now takes the project lock before stopping, as a consistent export does, and a failed restart is no longer retried a second time by the deferred one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
🔍 Code ReviewPR #4894 · 1 · Back up now button never rendered
2 · S3 destinations in use by project backups could be deleted or moved
3 · Local external volumes could not be selected in the backup dialog
4 · Restart ignored Compose dependency order
Low and informational (11)
🤖 Claude Opus 5.5 (High) · T3 Code (Claude Code) · Round 2 of 3 |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings in main's frontend query cleanup through getarcaneapp#4888. The Backups tab joins the rebuilt tab list, and the backups list call is typed for the new API client. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The export dialog fetched its options from an $effect that wrote state. It now uses a project query enabled while the dialog is open, refetched on every open so in-use and running state is current. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings in getarcaneapp#4893. Transfer keeps the shared volume classification and skips named volumes missing on the source, as getarcaneapp#4893 does; the restore keeps getarcaneapp#4893's empty-archive rule and the created-volume result. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
| stopped, stopErr = s.deps.StopContainers(ctx, project.ComposeName) | ||
| p.Stopped = checkpointContainers(stopped) | ||
| if recordErr := errors.Join(stopErr, s.record(ctx, p)); recordErr != nil { |
There was a problem hiding this comment.
Crashes can leave projects stopped. The recovery list is saved only after
StopContainers returns. If Arcane is killed while that call is stopping a multi-container project, Docker has already stopped some containers but the saved Stopped list is still empty. The resumed run cannot tell those containers need restarting. Save the recovery set before issuing the stops.
Prompt To Fix With AI
This is a comment left during a code review.
Path: backend/internal/project/children/backup/service.go
Line: 544-546
Comment:
**Crashes can leave projects stopped.** The recovery list is saved only after `StopContainers` returns. If Arcane is killed while that call is stopping a multi-container project, Docker has already stopped some containers but the saved `Stopped` list is still empty. The resumed run cannot tell those containers need restarting. Save the recovery set before issuing the stops.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.| project, err := s.deps.Project(ctx, entry.ProjectID) | ||
| if err != nil { | ||
| return err | ||
| } |
There was a problem hiding this comment.
Queued backups use old volumes.
StartBackup freezes p.Volumes before taking the project lock, but capture reloads the project's current files. A compose edit and deploy can finish while the backup is queued or waiting for that lock. If they switch the project to another volume, the backup can succeed with the new compose file and the old volume's data. Check the plan against the locked project before capture, then reject or rebuild it with matching volume locks and leases.
Prompt To Fix With AI
This is a comment left during a code review.
Path: backend/internal/project/children/backup/service.go
Line: 506-509
Comment:
**Queued backups use old volumes.** `StartBackup` freezes `p.Volumes` before taking the project lock, but `capture` reloads the project's current files. A compose edit and deploy can finish while the backup is queued or waiting for that lock. If they switch the project to another volume, the backup can succeed with the new compose file and the old volume's data. Check the plan against the locked project before capture, then reject or rebuild it with matching volume locks and leases.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.| db.Table("system_backup_policies").Where("s3_destination_id = ? AND s3_enabled = ?", id, true), | ||
| db.Table("volume_backups").Where("s3_destination_id = ? AND remote_snapshot_id <> ''", id), | ||
| db.Table("volume_backup_policies").Where("s3_destination_id = ? AND s3_enabled = ?", id, true), | ||
| db.Table("project_backups").Where("s3_destination_id = ? AND remote_snapshot_id <> ''", id), |
There was a problem hiding this comment.
Active S3 destinations remain editable. On the first manual backup to a destination,
s3_destination_id is set but remote_snapshot_id stays empty until the S3 write finishes. This filter lets the destination change or be deleted during that write. The snapshot can finish in the old bucket while its row points at the changed or deleted destination, leaving the backup unreachable. Count running project backups as references too.
Prompt To Fix With AI
This is a comment left during a code review.
Path: backend/internal/s3/service.go
Line: 262
Comment:
**Active S3 destinations remain editable.** On the first manual backup to a destination, `s3_destination_id` is set but `remote_snapshot_id` stays empty until the S3 write finishes. This filter lets the destination change or be deleted during that write. The snapshot can finish in the old bucket while its row points at the changed or deleted destination, leaving the backup unreachable. Count running project backups as references too.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.| func SelectComposeFiles(ctx context.Context, selection ComposeFileSelection) error { | ||
| if slices.Equal(selectedComposeFiles(ctx, selection.GlobalEnvDirectory, selection.ProjectPath), selection.Files) { | ||
| return nil | ||
| } |
There was a problem hiding this comment.
Imports change Compose overrides. This equality check loses whether
COMPOSE_FILE explicitly selected one file. For a source with .env.global setting COMPOSE_FILE=compose.yaml and an unused compose.override.yaml, the bundle records only compose.yaml. On a destination without that global setting, this early return leaves COMPOSE_FILE unset, so Compose now merges the override. The import can succeed with different images, commands, or settings. Preserve the exact loaded file set and whether automatic overrides apply.
Prompt To Fix With AI
This is a comment left during a code review.
Path: backend/pkg/projects/env.go
Line: 836-839
Comment:
**Imports change Compose overrides.** This equality check loses whether `COMPOSE_FILE` explicitly selected one file. For a source with `.env.global` setting `COMPOSE_FILE=compose.yaml` and an unused `compose.override.yaml`, the bundle records only `compose.yaml`. On a destination without that global setting, this early return leaves `COMPOSE_FILE` unset, so Compose now merges the override. The import can succeed with different images, commands, or settings. Preserve the exact loaded file set and whether automatic overrides apply.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.| SELECT 1 FROM api_key_permissions AS reader | ||
| WHERE reader.api_key_id = source.api_key_id | ||
| AND reader.permission = 'projects:read' | ||
| AND COALESCE(reader.environment_id, '') = COALESCE(source.environment_id, '') |
There was a problem hiding this comment.
Mixed scopes miss backup grants. The new grant requires matching
environment_id values, but permission checks combine global and per-environment grants. A scoped key with global projects:read and volumes:backup for one environment has both prerequisites there, yet gets no projects:backup row. Handle these mixed scopes in both SQLite and Postgres so the migration grants the permission over their shared environments.
Prompt To Fix With AI
This is a comment left during a code review.
Path: backend/internal/database/migrations/00118_project_backups.go
Line: 46-49
Comment:
**Mixed scopes miss backup grants.** The new grant requires matching `environment_id` values, but permission checks combine global and per-environment grants. A scoped key with global `projects:read` and `volumes:backup` for one environment has both prerequisites there, yet gets no `projects:backup` row. Handle these mixed scopes in both SQLite and Postgres so the migration grants the permission over their shared environments.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.| if p.S3DestinationID = strings.TrimSpace(request.S3DestinationID); p.S3DestinationID == "" { | ||
| return plan{}, common.Classify(common.ErrBadRequest, errors.New("select an S3 destination for the project backup")) |
There was a problem hiding this comment.
Plan fields change after creation.
resolvePlan builds p, then fills S3DestinationID, Volumes, and the inspected volume fields afterward. The Go rule requires one keyed literal per value, with known fields set inside it. Resolve and validate these inputs first, then build the inspected entries and final plan with literals.
Rule Used: --- name: go-struct-literals description: Write Go 1.27+ in a declarative, composite-literal style. Every value (structs, slices, maps, configs, errors, servers, test tables, constructor results) is built with one keyed composite literal instead of f... (source)
Prompt To Fix With AI
This is a comment left during a code review.
Path: backend/internal/project/children/backup/service.go
Line: 204-205
Comment:
**Plan fields change after creation.** `resolvePlan` builds `p`, then fills `S3DestinationID`, `Volumes`, and the inspected volume fields afterward. The Go rule requires one keyed literal per value, with known fields set inside it. Resolve and validate these inputs first, then build the inspected entries and final `plan` with literals.
**Rule Used:** --- name: go-struct-literals description: Write Go 1.27+ in a declarative, composite-literal style. Every value (structs, slices, maps, configs, errors, servers, test tables, constructor results) is built with one keyed composite literal instead of f... ([source](https://app.greptile.com/-/switch-tenant?tenant=getarcaneapp&next=%2Fcustom-context%3Fmemory%3D214b40a8-9695-4738-986d-5949b5d65ff1))
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
| // projectBundles exports and imports projects with their volume data through the volume operations injected for transfers. | ||
| projectBundles struct { | ||
| local localTransferEnvironment | ||
| activity activity.MessageAppender |
There was a problem hiding this comment.
Unused activity dependency. The new
projectBundles.activity field is never read, but New and the tests still wire it in. Remove the field, its import, and its wiring so bundle code does not advertise a dependency it never uses.
Prompt To Fix With AI
This is a comment left during a code review.
Path: backend/internal/project/service.go
Line: 208
Comment:
**Unused activity dependency.** The new `projectBundles.activity` field is never read, but `New` and the tests still wire it in. Remove the field, its import, and its wiring so bundle code does not advertise a dependency it never uses.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
A project whose only active containers were in a restart loop looked stopped: the export dialog hid the stop switch and the bundle was marked consistent while those containers could still write their volumes. The export preview and the consistency check now count running and restarting containers, the same ones a stop stops. ComposeVolumeTargetName also takes an options struct instead of four ordered strings. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A live backup of a project whose only active containers were in a restart loop was marked consistent. It now uses the same running or restarting check as export. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
| } | ||
|
|
||
| // Export packages the project archive and the data of the requested volumes into a bundle upload session. | ||
| func (b projectBundles) Export(ctx context.Context, opts ExportBundleOptions) (*types.UploadSession, error) { |
There was a problem hiding this comment.
Bundle code ignores feature layout.
projectBundles adds export, import, volume restore, and rollback logic to the parent service.go. AGENTS.md requires substantial features under children/<feature>/ and one job per file. Move this bundle code into a project child and keep the parent focused on connecting it to project operations.
Context Used: AGENTS.md (source)
Prompt To Fix With AI
This is a comment left during a code review.
Path: backend/internal/project/service.go
Line: 1832
Comment:
**Bundle code ignores feature layout.** `projectBundles` adds export, import, volume restore, and rollback logic to the parent `service.go`. `AGENTS.md` requires substantial features under `children/<feature>/` and one job per file. Move this bundle code into a project child and keep the parent focused on connecting it to project operations.
**Context Used:** AGENTS.md ([source](https://github.com/getarcaneapp/arcane/blob/main/AGENTS.md))
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
Important
PR 4 of 4. Merge in order: #4876 (merged) → #4879 → #4888 → this PR. It is stacked on #4888, so the diff looks large: it includes #4879's and #4888's changes until those merge. Only this PR's changes.
Checklist
mainbranchm.*())What This PR Implements
Part of #4880 (phases 1 and 2 of the plan there). Restore, schedules and the system backup split come in later PRs, so this doesn't close the issue.
A project can now be backed up as one Rustic snapshot holding its files and the data of its volumes, so both come from the same point in time. Backups can be listed and deleted from a new Backups tab on the project page. Volume and system backups behave as before.
Changes Made
Snapshot (
internal/project/children/backup, new child domain):backup.Engine. The project directory is mounted atproject/, each selected volume atvolumes/<docker volume name>/, and the manifest atmeta/arcane-project.json, all read-only.types.ProjectManifestwithkind: "backup". Volume selection is feat: export and import projects with their volumes #4888'sClassifyProjectVolumes: named and local external volumes that exist are included by default; volumes with driver options are listed but not backed up.arcane-kind:project,arcane-project:<id>,arcane-run:<id>.Consistency:
stopContainersis on by default. The backup takes the project lock (as a consistent export does), stops only this project's running and restarting containers, and starts them again through Compose in dependency order, on every path including errors.consistent.Admission: scope
project-backupper project, plus thevolume-backuplease and volume lock for each captured volume, so a project backup can't overlap a per-volume backup or restore of the same volume. Manual runs fail fast with a conflict.Shared plumbing moved into
internal/backup(no behaviour change): the volumes repository builders and password, container stop/start for volume backups, and source-mount resolution used by system snapshots. Volume discovery now skipsarcane-kind:projectsnapshots, so they never show up as volume backups.API (
/agents/{id}/projects/{projectId}/backups):POST({volumes?, stopContainers?, destination?, s3DestinationId?}),GETlist (paginated, newest first),GET /{backupId},DELETE /{backupId}(forgets the snapshots and deletes the row). The routes are on the agent allowlist, so remote environments work.Permissions and data: new
projects:backup. Migration00118createsproject_backupsand grantsprojects:backupto roles and API keys that already havevolumes:backupandprojects:read, with a real down migration. Deleting an S3 destination counts project backups as in use.UI: a Backups tab (the existing
backuptab is the Git push-back feature) listing date, status, volumes, destination and size, with a mobile card layout. Back up now opens a dialog with the same volume rules as the export dialog, the stop-containers toggle and the destination select. Delete asks for confirmation.Testing Done
just format all,just lint all(0 issues; svelte-check 0 errors),go build -tags exclude_frontend ./....consistentruleinternal/backuphelpers (their tests moved with them)consistent: falsebecause of that container.AI Tool Used (if applicable)
Claude Code (Claude Opus 5.5) planned and implemented this, ran the local review and the evidence, and drafted this description, at my direction.
Additional Context
🤖 Generated with Claude Code
📸 Evidence
Before
main@8612ea241→ Afterfeat/4880-project-backups@fb62d63e2· Arcane with a seeded test project evidence-shop (nginx + busybox; named volumes site and cache, and a local external volume evidence-shared) on a sandbox Docker engine, plus evidence-other, a standalone container that also mounts evidence-shared; test account only, no private data. After captured from fb62d63; Before is main, because #4888 doesn't change the project tabs🖥️ Project tabs — desktop
8612ea241fb62d63e2🎬 Backups tab and Back up now dialog — recording, 0:07
🎬 Backups tab and dialog on a phone — recording, 0:09
🔌 API response —
POST /api/agents/0/projects/{id}/backups {}, trimmed to changed fields📸 Captured by Claude Opus 5.5 (High) · T3 Code (Claude Code) · Playwright · Chromium (mcr.microsoft.com/playwright, --docker); Arcane images built with docker/Dockerfile; rustic v0.11.2 for the snapshot listing · 2026-11-19 02:25 UTC
Disclaimer Greptiles Reviews use AI, make sure to check over its work.
To better help train Greptile on our codebase, if the comment is useful and valid Like the comment, if its not helpful or invalid Dislike
To have Greptile Re-Review the changes, mention
greptileai.Not ready to merge: a crash during backup can still leave project containers stopped.
Fix with agent prompt
Summary
Adds manual project backups that keep project files and selected volume data in one snapshot, with local and S3 storage and a Backups tab.
Review was static; tests were not rerun.
Reviews (2) · Last reviewed commit: "fix: treat restarting containers as runn..." · Reviewed by Greptile