Commit Graph
2 Commits
Author SHA1 Message Date
Bastien ChanotandClaude Opus 4.7 7dd4f633f8 chore: rename project from osteo-report to zoosteo
Remote moved to git.bchanot.fr/bchanot/zoosteo.git; brand strings
and production URL updated to match new identity.

- package.json: name → zoosteo
- src/config/env.ts: AppConfig DEFAULTS → "Zoosteo"
- docker/entrypoint.sh: APP_*_NAME fallbacks → "Zoosteo"
- src/i18n/{fr,en}.ts: import error message + PDF title prefix
- src/pdf/attachment.ts: embedded description metadata "state v2"
- index.html: <title> fallback
- scripts/scaffold-species.mjs: console banner
- tests/unit/components.Brand.test.tsx: regex
- README.md, CLAUDE.md, CHANGELOG.md, docs/ADDING-A-SPECIES.md:
  brand headings + intro lines
- DEPLOY.md: env defaults table + osteo.example.com → zoosteo.fr
  (clone URL, paths, certbot, curl, container name references)

PDF attachment FILENAME 'osteo-report.json' and the startsWith
contract in src/pdf/attachment.ts:35,40 are preserved — changing
them would break PDF import for every PDF already exported by the
app. docs/superpowers/** and .claude/audits/** left unchanged as
historical records.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-21 05:53:12 +02:00
Bastien Chanot 98117b3b7f docs: add DEPLOY.md — VPS deploy guide (Docker + nginx + Certbot)
Production deploy playbook for Osteo Report. Single nginx:alpine
container behind a host reverse proxy; no backend, no database, no
server-side state. Praticien data lives in the browser and in the
exported PDFs themselves.

Sections cover:
- Topology + container/host port table.
- Required environment (.env): APP_SITE_NAME / BRAND_NAME /
  FOOTER_NAME / TAGLINE + optional PORT. No secrets.
- VPS provisioning (Ubuntu 24.04 LTS, 1 vCPU / 1-2 GB RAM, DNS,
  baseline apt packages).
- Firewall — cloud provider security group + UFW on the VM, with
  explicit "do NOT expose 8080" note.
- Docker install + tuned daemon.json (json-file log driver capped
  10MB × 5, live-restore).
- First-time setup, routine deploys via `git fetch + reset --hard
  origin/master + docker compose up --build -d`.
- Data persistence + backups: just the .env file (no volumes).
  Daily cron + retention + off-VPS sync.
- TLS reverse proxy — Option A (host nginx + Certbot with security
  headers HSTS/XFO/XCTO/Referrer-Policy/Permissions-Policy/CSP),
  Option B (Caddy auto-TLS Caddyfile).
- Sanity checks — TLS redirect, env.js cache headers, no-public-8080
  verification via nc + nmap.
- Hardening — non-root deploy user, disable root + password SSH,
  optional SSH port move, unattended security upgrades, fail2ban,
  external lockdown nmap.
- Rollback (git reset + rebuild — no data to restore).
- Health checks table, troubleshooting (9 common failures with
  recipes), operational notes (log destinations, manual prune,
  provider-specific RAM hints).

README.md DEPLOY.md link now points at a real document.
2026-05-21 04:13:28 +02:00