From 84a0882d32831bb79536548c46b6e845a141f2a2 Mon Sep 17 00:00:00 2001 From: Sylvain Duchesne Date: Mon, 12 Oct 2026 10:37:35 +0200 Subject: [PATCH] =?UTF-8?q?Document=20the=20root=20.env=20copy=20for=20man?= =?UTF-8?q?ual=20app=20serving=20=E2=80=94=20without=20it=20the=20app=20fa?= =?UTF-8?q?lls=20back=20to=20the=20local=20demo?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../concepts/data-layer/cookbook_local-activitypods-platform.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.project/concepts/data-layer/cookbook_local-activitypods-platform.md b/.project/concepts/data-layer/cookbook_local-activitypods-platform.md index 697e922..30fe223 100644 --- a/.project/concepts/data-layer/cookbook_local-activitypods-platform.md +++ b/.project/concepts/data-layer/cookbook_local-activitypods-platform.md @@ -17,7 +17,7 @@ pod provider 3000 (OpenID + `/auth` signup/login), Festipod backend 3003, Festip 2. Install once: `cd backend && COREPACK_ENABLE_AUTO_PIN=0 corepack yarn install --frozen-lockfile`, same in `frontend/`. Keep `COREPACK_ENABLE_AUTO_PIN=0`: corepack auto-pin rewrites `packageManager` in package.json. Note: the pod-provider README says `yarn start` for the frontend; only the `dev` script exists — use `BROWSER=none corepack yarn dev`. 3. Backend: `cd backend && corepack yarn start`. Wait for "ServiceBroker with ... service(s) started successfully" (~11 s). 4. Frontend: `cd frontend && BROWSER=none corepack yarn dev`. Verify: `GET http://localhost:5000/` → 200 and `GET http://localhost:3000/.well-known/config.js` → 200. -5. Festipod stack (this repo root): `cp backend/.env.example backend/.env` before `docker compose up`. The compose reads `backend/.env` as an optional `env_file`; on a fresh clone the file is gitignored and absent, so this copy is what feeds the backend its ActivityPods settings. With the coherent layout the app is served on :4000 and the Festipod backend on :3003 — keep the pod provider frontend (which owns :5000) stopped while testing Festipod. +5. Festipod stack (this repo root): `cp backend/.env.example backend/.env` before `docker compose up`. The compose reads `backend/.env` as an optional `env_file`; on a fresh clone the file is gitignored and absent, so this copy is what feeds the backend its ActivityPods settings. With the coherent layout the app is served on :4000 and the Festipod backend on :3003 — keep the pod provider frontend (which owns :5000) stopped while testing Festipod. To serve the app manually (`bun run start` on :4000) ALSO copy the root env: `cp .env.example .env` — without `VITE_BACKEND_URL` the config route serves an empty backend URL and the app deliberately falls back to the local demo (seeded data, no login). ## Account and resource flow (all VERIFIED 2026-10-09)