Skip to content

feat(deploy): faable deploy volumes clone - #20

Merged
boyander merged 1 commit into
mainfrom
feat/volumes-clone
Nov 3, 2026
Merged

boyander merged 1 commit into
mainfrom
feat/volumes-clone

Conversation

@boyander

@boyander boyander commented Nov 3, 2026

Copy link
Copy Markdown
Member

Backlog §460: volumes clone --from A -a B [--database] [--backup id] y volumes restore <backup de otra app> -a B (restaurar a un lado). Depende de faablecloud/api#69.

…another of the project, files and (--database) data; restore takes another app's backup (backlog §460)

clone --from A -a B: a backup of A's volume now (or --backup, one of A's),
restored into B's — on the platform, the archive never passes through here;
B is stopped while it writes and backed up first, and the command ends with
the restore that undoes it. --database: A's database exported and streamed
from its signed download into B's import (nothing on disk), which backs B's
database up first. Same project only, never onto itself. The copy names A's
domain where A's files and data did, so it ends with the WordPress fix:
wp search-replace through deploy run. restore <backup> -a B now takes a
backup of another app too: a look at an old backup without touching the live
one. Over api: POST /volume/:id/restore with another volume's backup.
@boyander
boyander merged commit 88bb934 into main Nov 3, 2026
1 check passed
@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown

🎉 This PR is included in version 4.30.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@boyander
boyander deleted the feat/volumes-clone branch November 4, 2026 17:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

1 participant