Public: anyone can read this; the crew can change it.

gretchy-stretchy moves to the forge and keeps working: its data, its domain and its payments #11687

shipped production is serving it opened this has it

Landed in pull #11857 · 2 runs · run

opened this

Why. Owner: "gretchy-strechy could be migrated to the forge. i want that app to survive." It runs today as a platform app on the DigitalOcean node (otavert--gretchy-stretchy--prod, its own Postgres, the domain gretchy.store through the platform's edge). When that node goes, it goes, unless it has moved.

What. Use the forge's own migration path (migrate, #643–#649) and make it good enough for a real shop:

  • Inventory first, read-only: its repository, its database (tables, sizes, row counts), its files and uploads, its environment and secrets (names only), its domain and DNS, its payment setup, its scheduled jobs, who signs in to it.
  • The app runs on the forge from its repository; its data is copied with counts and checksums compared; files copied; secrets set by the owner (never read out); schedules declared in forge.json.
  • A rehearsal on a preview address with a copy of the data, checked by a person (the owner or the shop's owner) before any cut-over.
  • The domain moves last, at a quiet hour, with the old app left running read-only for a week and a one-step way back.
  • An encrypted backup of the old database and files is taken and a restore is proven before the old copy is ever removed.
  • Write down everything the platform app relied on that the forge lacks; each becomes an issue, because the next platform app will need it too.

Acceptance. gretchy.store is served by the forge with the same data (counts and checksums match), an order can be placed in its payment sandbox on the rehearsal and in live after cut-over, and the old copy is still restorable. The owner says go before the domain moves.

commented

Steward, 2026-11-13 06:25Z. gretchy-stretchy is now safe off the DigitalOcean box and its source is on this forge, so the port can start from facts:

  • Source: private repo trevato/gretchy-stretchy on this forge (all branches and tags pushed from the platform's Forgejo, main at 671707e).
  • What it is on the platform: image otavert/gretchy-stretchy:0.1.14 (an old platform-template app), Postgres 18 (database 8.4 MB: shop_products 10 rows, shop_settings 1, shop_cart_items 1, shop_orders 0, order_items 0, plat_audit 61), an empty /data volume, sign-in through the platform's forwardAuth (env PLAT_FORWARD_AUTH, PLAT_EDGE_TOKEN), domain gretchy.store through Cloudflare.
  • Archived on the vxrail under /srv/forge-archive/gretchy (the steward can read it, the crew cannot): a pg_dump taken with no orders in flight, the image, the bare repo.

What the port needs, in order: (1) the storefront running as a forge app from the app template (SQLite; the ten products and the one settings row imported from the dump: the steward will supply them as JSON on request here); (2) the admin side signing in with the forge's own accounts, no forwardAuth; (3) checkout through the template's payments seam (app-template #10/#19) or off with a plain "not taking orders yet" until a Stripe key is set, never a broken button; (4) the domain gretchy.store moved to the forge app as a custom domain, which the steward does once (1) answers on its forge address. Done when gretchy.store serves the same ten products from the forge and the platform namespace can be deleted.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs