webapp/nginx.conf.example
Padreug 5541d2bc7a refactor(events): rename activities module to events + wire VITE_APP_NAME for per-deployment branding (#94)
## Why

The module was named `activities` originally to avoid colliding with Nostr's `Event` type. In practice that defense added friction without preventing confusion — the backend extension is named `events`, NIP-52 calls them "Calendar Events", and the UI already displayed "Events". The collision with `nostr-tools` `Event` is handled cleanly by the existing `import { Event as NostrEvent }` alias pattern (already in 5 files inside the module). Renaming collapses the 4-way mismatch into one consistent term.

Separately, deployments needed per-instance app names. `VITE_APP_NAME` was already plumbed per-standalone via NixOS `services.webapp-standalones.<app>.displayName` (e.g. cfaun shipped `"Sortir"`, now rebranded to `"Bouge"`), but nothing in the standalone consumed it — PWA manifest, HTML title, and runtime branding were all hardcoded. This PR wires the env through every app-name display point so any deploy can flip `displayName = "Bouge"` (or anything) and pick up the brand end-to-end.

## What

Nine commits on the branch:

1. **`refactor(events): rename activities module to events`** — 70-file rename. `src/modules/activities/` → `src/modules/events/`, `src/activities-app/` → `src/events-app/`, types/services/composables/views/components/store renamed (`Activity`→`Event`, `Activities`→`Events`). Routes `/activities/*` → `/events/*`; the legacy `/events` (ticketing management) moves to `/my-events` so `/events` belongs to the canonical feed. DI tokens `ACTIVITIES_*` → `EVENTS_*`. i18n namespace renamed; English domain strings updated, French/Spanish title key realigned. npm scripts `:activities` → `:events`. Build output `dist-activities/` → `dist-events/`.

2. **`feat(events): wire VITE_APP_NAME through PWA manifest, HTML, runtime`** — PWA manifest `name`/`short_name` template from `process.env.VITE_APP_NAME` with fallback `'Events'`. `events.html` uses Vite's `%VITE_APP_NAME%` substitution. `src/events-app/app.ts` + `main.ts` runtime brand string drives console logs, offline notification, and `acceptTokenFromUrl()`. `events.title` route meta sources from VITE_APP_NAME. `.env.example` updated with per-standalone scoping notes.

3. **`docs(events): update activities→events references`** — `docs/nostr-patterns/*.md` "Canonical: src/modules/activities/composables/useRSVP.ts" anchors point at renamed paths. CLAUDE.md Payment Rails Pattern section updated.

4. **`fix(events): drop lowercase from PWA description brand name`** — minor casing fix caught during verification.

5. **`fix(events): use domain noun in description, not brand name`** — manifest + HTML description switched from `"Discover ${BRAND} near you"` to static `"Discover events near you"`. Description is about *what* the app does, not the brand.

6. **`chore(events): scrub leftover sortir/activities references`** — nginx.conf.example, package.json (concurrently process label + `build:demo` BASE_PATH), router-helpers comment, useMarket comment, and vite.events.config.ts doc-comment.

7. **`refactor(events): conditional brand in console label, tighten docs`** — adds `APP_LABEL` next to `APP_NAME` in `events-app/app.ts`. Reads as `Events` on unbranded builds and `Events (Bouge)` (etc.) when `VITE_APP_NAME` is set to anything other than "Events" (case-insensitive). Used by all four console messages; `acceptTokenFromUrl` keeps the raw `APP_NAME` (it's a token-namespace identifier, not display copy). Also collapses the redundant "cfaun sets X; future deployments can override (e.g. X)" doc-comment.

8. **`i18n(events): finish activité/actividad → événement/evento sweep`** — completes the i18n rename in fr.ts and es.ts (search placeholders, favorites prompts, settings prompt) and fixes five gender-agreement errors that came along with the masculine `événement`/`evento` switch (French: `Aucune ... trouvée`→`Aucun ... trouvé`, `préférées`→`préférés`, `d'une ... la sauvegarder`→`d'un ... le sauvegarder`; Spanish: `favoritas`→`favoritos`, `guardarla`→`guardarlo`).

9. **`chore(events): finish sortir → bouge sweep in .env.example`** — four remaining doc-comment refs in `.env.example` (cfaun branding, ticket-scanner comment, section header, subdomain-mode URL example).

## Cross-repo coordination

This PR has matching changes already pushed to two other repos. They have to land in a coordinated bump because the names are tightly coupled.

- **`aiolabs/webapp-module` main** — commit `9d82016`. Renames `hubActivitiesUrl` → `hubEventsUrl` and `VITE_HUB_ACTIVITIES_URL` → `VITE_HUB_EVENTS_URL`. No backwards-compat shim.
- **`aiolabs/server-deploy` main** — commits `f15e1eb`, `bf4698b`, `d46a520`:
  - `standalones.nix` `apps.events` uses `build:events` / `dist-events` / `events.html`; `hubUrlOption` maps `events → "hubEventsUrl"`; comment + cfaun-as-example doc switched from sortir/Sortir to bouge/Bouge.
  - `hosts/cfaun/default.nix` rebranded: `subdomain = "bouge"` + `displayName = "Bouge"`. (Native-French feedback retired the "Sortir" branding as awkward.)
  - `hosts/atio/default.nix` stale "activities app" comment dropped (atio's `displayName = "Eventos"` config is unchanged).

server-deploy's `flake.lock` still pins the OLD webapp + OLD webapp-module, so nix builds from server-deploy main will fail until the bumps. Suggested order after this PR merges to `dev`: one server-deploy commit that does `nix flake lock --update-input webapp-module` + `--update-input webapp-demo` together. DNS for `bouge.ariege.io` needs to point at the cfaun host before the deploy lands.

## Verification

- `pnpm typecheck` — clean ✓
- `pnpm build:events` (default) — `dist-events/manifest.webmanifest` has `name: "Events"`, description "Discover events near you" ✓
- `VITE_APP_NAME=Bouge pnpm build:events` — `name: "Bouge"`, HTML title "Bouge", console label resolves to `Events (Bouge)` ✓
- Cross-repo grep sweep: no `Sortir`/`sortir`/`activities`/`Activities` references in events-module scope. (Domain false positives — "Market Activity" in market dashboard, "time-based activities" in nostr-feed content filters, "Activity Lifecycle Kills" in CLAUDE.md mobile-browser docs — are unrelated and intentionally left alone.)

Not verified in-browser (no GUI in this session) — needs a manual smoke at `app.ariege.io/bouge/` once the coordinated flake bump lands on cfaun. Watch for: feed loads, `/events/calendar`, `/events/map`, `/events/favorites`, `/events/:id` routes work; "My Events" appears in the user dropdown and `/my-events` shows the management page; PWA install prompt shows "Bouge".

## Out of scope (deferred)

- Backend extension rename — `aiolabs/events` is already named correctly.
- Nix standalone attribute name — `services.webapp-standalones.events` is already correct.
- Overriding domain-noun strings ("Your event was created", RSVP labels) — those stay locale-driven; `VITE_APP_NAME` covers app-name only.
- Backwards-compat redirects from `/activities/*` to `/events/*` — pre-launch, public URL was `/sortir/` (path-mode) or `sortir.ariege.io` (subdomain-mode), never `/activities/`. No external bookmarks to preserve. (`sortir.ariege.io` → `bouge.ariege.io` is a separate decision; up to the deploy operator whether to keep a 301 for word-of-mouth referrers.)

Reviewed-on: #94
2026-06-09 18:18:26 +00:00

169 lines
8.4 KiB
Text

# Main context
worker_processes auto;
events {
worker_connections 1024;
}
http {
default_type application/octet-stream;
set_real_ip_from 0.0.0.0;
real_ip_header X-Forwarded-For;
real_ip_recursive on;
# ───────────────────────────────────────────────────────────────────────
# PATH-MODE deployment (recommended)
#
# demo.<domain>.<com>/ — minimal AIO chakra hub
# demo.<domain>.<com>/events/ — events standalone
# demo.<domain>.<com>/market/ — marketplace standalone
# demo.<domain>.<com>/wallet/ — wallet standalone
# demo.<domain>.<com>/chat/ — chat standalone
# demo.<domain>.<com>/forum/ — forum standalone
# demo.<domain>.<com>/tasks/ — tasks standalone
# demo.<domain>.<com>/libra/ — libra (accounting) standalone
#
# Each standalone is built with VITE_BASE_PATH=/<name>/ so its asset URLs
# are prefixed correctly. The hub's chakra tiles point at the canonical
# trailing-slash path (VITE_HUB_<NAME>_URL=https://demo.<domain>/<name>/).
#
# Per-app no-trailing-slash → with-slash 301 redirects exist for users
# who hand-type the URL or follow a stripped-slash link.
#
# All static assets (JS / CSS / images / SVGs) are MIME-typed and image
# types get a 6-month cache-control.
# ───────────────────────────────────────────────────────────────────────
server {
listen 8080;
server_name demo.<domain>.<com>;
# Hub at the root
root /var/www/aio/dist;
index index.html;
location = / { try_files $uri /index.html; }
location / {
# Default: serve from hub bundle if no /<app>/ prefix matched.
try_files $uri $uri/ /index.html;
}
# ── Events ──────────────────────────────────────────
location = /events { return 301 /events/$is_args$args; }
location /events/ {
alias /var/www/aio/dist-events/;
try_files $uri $uri/ /events.html;
}
# ── Market ───────────────────────────────────────────────────────
location = /market { return 301 /market/$is_args$args; }
location /market/ {
alias /var/www/aio/dist-market/;
try_files $uri $uri/ /market.html;
}
# ── Wallet ───────────────────────────────────────────────────────
location = /wallet { return 301 /wallet/$is_args$args; }
location /wallet/ {
alias /var/www/aio/dist-wallet/;
try_files $uri $uri/ /wallet.html;
}
# ── Chat ─────────────────────────────────────────────────────────
location = /chat { return 301 /chat/$is_args$args; }
location /chat/ {
alias /var/www/aio/dist-chat/;
try_files $uri $uri/ /chat.html;
}
# ── Forum ────────────────────────────────────────────────────────
location = /forum { return 301 /forum/$is_args$args; }
location /forum/ {
alias /var/www/aio/dist-forum/;
try_files $uri $uri/ /forum.html;
}
# ── Tasks ────────────────────────────────────────────────────────
location = /tasks { return 301 /tasks/$is_args$args; }
location /tasks/ {
alias /var/www/aio/dist-tasks/;
try_files $uri $uri/ /tasks.html;
}
# ── Libra (accounting) ──────────────────────────────────────────
location = /libra { return 301 /libra/$is_args$args; }
location /libra/ {
alias /var/www/aio/dist-libra/;
try_files $uri $uri/ /libra.html;
}
# ── Static asset MIME / cache (applies to all bundles) ───────────
location ~* \.js$ { types { application/javascript js; } default_type application/javascript; }
location ~* \.css$ { types { text/css css; } default_type text/css; }
location ~* \.(png|jpe?g|webp|ico|svg)$ { expires 6M; access_log off; }
}
# ───────────────────────────────────────────────────────────────────────
# Optional subdomain shortcuts → canonical path
#
# If you want pretty subdomain URLs that funnel into the path-mode
# canonical, add 301 redirects per app. Example:
#
# events.demo.<domain>.<com> → demo.<domain>.<com>/events/
# market.demo.<domain>.<com> → demo.<domain>.<com>/market/
# ───────────────────────────────────────────────────────────────────────
server {
listen 8080;
server_name events.demo.<domain>.<com>;
return 301 https://demo.<domain>.<com>/events/$request_uri;
}
server {
listen 8080;
server_name market.demo.<domain>.<com>;
return 301 https://demo.<domain>.<com>/market/$request_uri;
}
server {
listen 8080;
server_name wallet.demo.<domain>.<com>;
return 301 https://demo.<domain>.<com>/wallet/$request_uri;
}
server {
listen 8080;
server_name chat.demo.<domain>.<com>;
return 301 https://demo.<domain>.<com>/chat/$request_uri;
}
server {
listen 8080;
server_name forum.demo.<domain>.<com>;
return 301 https://demo.<domain>.<com>/forum/$request_uri;
}
server {
listen 8080;
server_name tasks.demo.<domain>.<com>;
return 301 https://demo.<domain>.<com>/tasks/$request_uri;
}
server {
listen 8080;
server_name libra.demo.<domain>.<com>;
return 301 https://demo.<domain>.<com>/libra/$request_uri;
}
# ───────────────────────────────────────────────────────────────────────
# SUBDOMAIN-MODE deployment (alternative — pure subdomains, no /path/)
#
# If you'd rather give each standalone its own subdomain and skip the
# path-mode entirely:
#
# server { server_name app.<domain>; root /var/www/aio/dist; ... }
# server { server_name market.<domain>; root /var/www/aio/dist-market; ... }
# server { server_name events.<domain>; root /var/www/aio/dist-events; ... }
# server { server_name wallet.<domain>; root /var/www/aio/dist-wallet; ... }
# server { server_name chat.<domain>; root /var/www/aio/dist-chat; ... }
# server { server_name forum.<domain>; root /var/www/aio/dist-forum; ... }
# server { server_name tasks.<domain>; root /var/www/aio/dist-tasks; ... }
# server { server_name libra.<domain>; root /var/www/aio/dist-libra; ... }
#
# Each block uses `location / { try_files $uri $uri/ /<name>.html; }`.
# In subdomain mode, build each standalone WITHOUT VITE_BASE_PATH (the
# default `/` is correct), and set VITE_HUB_<NAME>_URL to the subdomain
# in the hub's env (e.g. VITE_HUB_MARKET_URL=https://market.<domain>).
# ───────────────────────────────────────────────────────────────────────
}