Serve the rebuild on app.coulomb.social; defer apex Bubble cutover
Document parallel-host strategy: Railiance on app.*, Bubble remains on coulomb.social until data and self-registration are ready.
This commit is contained in:
parent
fe8b96a388
commit
f5537d8365
4 changed files with 46 additions and 89 deletions
|
|
@ -23,7 +23,7 @@ This repository is the **owning home** for the rebuild:
|
|||
1. **Parity capture** — inventory and export everything that matters in the bubble.io app (UI surfaces, workflows, data types, content, integrations).
|
||||
2. **Cut decisions** — decide rebuild-as-is vs reduced v1 with an explicit human gate.
|
||||
3. **Implementation** — deliver a standalone service on the proven business delivery lane (`vergabe-teilnahme` evidence), under the business-app service contract.
|
||||
4. **Cutover** — migrate members and content off bubble.io when the new stack is ready.
|
||||
4. **Cutover** — serve the rebuild on **`app.coulomb.social`** in parallel with Bubble on apex `coulomb.social`; retire Bubble only when data, self-registration, and content parity are ready.
|
||||
|
||||
Binky Hedgehog GmbH is **client #1** of its own platform (DR-2 B). The app is not a Core Hub extension; it is a normal client-facing business application.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue