Compare commits

..

2 Commits

Author SHA1 Message Date
Julien Calixte
bd7613e2d0 docs: document dual Coolify and Pages deploy in README
Some checks failed
Deploy to GitHub Pages / build (push) Failing after 21s
Deploy to GitHub Pages / deploy (push) Has been skipped
2026-06-26 14:45:01 +01:00
Julien Calixte
01eece9796 docs: correct persistence backend to localStorage in README 2026-06-26 14:44:46 +01:00

View File

@@ -10,7 +10,7 @@ See [CONTEXT.md](./CONTEXT.md) for the domain glossary and [DESIGN.md](./DESIGN.
- Vite + Vue 3 + TypeScript
- Tailwind CSS v4 + DaisyUI
- Solo, browser-local persistence (IndexedDB or localStorage)
- Solo, browser-local persistence via localStorage
## Develop
@@ -22,4 +22,7 @@ pnpm build # production build into ./dist
## Deploy
Pushes to `main` are picked up by Coolify at https://platform.apoena.dev. The Dockerfile builds the SPA and serves it through nginx on port 80.
Every push to `main` triggers two independent deployments:
- **Coolify** (primary) — picked up at https://platform.apoena.dev and served at https://product-radar.apoena.dev. The Dockerfile builds the SPA and serves it through nginx on port 80, with `try_files … /index.html` as the history-mode SPA fallback.
- **GitHub Pages** — `.github/workflows/deploy-pages.yml` builds with pnpm and publishes `dist/`, copying `index.html` to `404.html` as the SPA fallback.