Bring an app from another forge (/bring)

Paste the link to an app on a forge you have connected (/settings/origins), and it comes across: the code and history are mirrored, it is registered as a private app and deploys at once, and you watch the first deploy on its app page. "Bring an app" is in the + menu and the palette.

to the author.

.env.example (names only, never values) and takes them in one form. Empty fields set nothing.

link to connect it; there is no anonymous fetch yet.

src/web/pages/bring.ts. Test: test/bring.test.ts.

What is left to bring over (/migrate/inventory)

Connect the account your apps live on (/migrate), then open /migrate/inventory: every repository of every connected origin, apps first.

Each row says what the repository holds, read from the repository itself: an app (forge.json or the platform's deploy file), a Postgres database, domains, and the names of its secrets, never a value (.env is never fetched). The badge is this forge's own record of the move: not started, migrating, in the forge, at parity, cut over.

A row not yet begun offers Bring into this forge (the migrate form with the repository chosen) and Into a new forge (the new-forge form named for it). A row already here offers Open here. The header's one primary button brings the next app over.

An origin that could not be reached is named above the list, so an empty list is never mistaken for an empty account. At most 40 repositories are read per visit, most recently pushed first; the rest say "Not read yet" and are read on a later visit. What was read is kept until the repository is pushed.

n starts a new forge, g reads again.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs