lronetto/wedding-app
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
This repository has been archived on 2026-06-09. You can view files and clone it, but cannot push or open issues or pull requests.
f882f8a1c8
wedding-app/.env.example

58 lines
2.2 KiB
Plaintext
Raw Normal View History

feat: full Docker stack on a VPS with improved admin editing Self-hosted rewrite of the wedding photo app: Node + Hono replaces Cloudflare Workers, Postgres 16 replaces D1, MinIO replaces R2, Caddy fronts the stack with automatic Let's Encrypt TLS. Same routes and feature set as before; storage abstraction is the same S3 client so MinIO drops in without code changes. Architecture: - docker-compose.yml: postgres, minio, minio-init (creates bucket + anonymous read + CORS), app, caddy (reverse proxy + media subdomain). - Dockerfile: multi-stage pnpm build, single runtime image serving the API and the SPA dist as static assets from one process. - Caddyfile: primary domain proxies to app; media subdomain proxies to MinIO so guests upload directly and signatures match Host. - app: tsx runtime, runs SQL migrations idempotently at startup via a schema_migrations(name, sha256, applied_at) table. Admin upgrades requested: - PATCH /api/admin/uploads/:id to edit author/message. - POST /api/admin/uploads/bulk for bulk approve/reject/delete. - POST /api/admin/uploads/:id/cover and DELETE /api/admin/event/cover to set/clear a featured image (rendered on Home when set). - GET /api/admin/uploads gains ?q= text search across author and message and ?kind=photo|video filter. - Dashboard: bulk select checkboxes with a toolbar, edit modal that rewrites author and message, search input, kind filter, set-cover button per item, cover preview + clear in the event card. Singletons replace the per-request bindings pattern: initDb() and initStorage() run once in server.ts; routes call getDb()/getStorage() directly rather than threading env.DB / env.MEDIA through. env.ts uses zod to parse process.env and fails fast if anything mandatory is missing. .env.example documents every variable and flags the hairpin tradeoff for MinIO access from the app container.
2026-06-07 19:11:10 -03:00
# =============================================================================
# Edite essas variáveis e salve como .env (mesmo diretório do docker-compose.yml)
# =============================================================================
# ----- Domínios (apontar DNS A/AAAA pra IP do VPS antes do `docker compose up`)
DOMAIN=casamento.exemplo.com.br
MEDIA_DOMAIN=midia.exemplo.com.br
ACME_EMAIL=voce@exemplo.com
# ----- Postgres
POSTGRES_USER=wedding
POSTGRES_PASSWORD=troque-isso-por-uma-senha-forte
POSTGRES_DB=wedding
# ----- MinIO (root credentials = também usadas pelo app como S3 access keys)
MINIO_ROOT_USER=minioadmin
MINIO_ROOT_PASSWORD=troque-isso-por-uma-senha-forte
S3_BUCKET=wedding-media
S3_REGION=us-east-1
# Endpoint INTERNO usado pelo app pra falar com o MinIO. Use o do Caddy
# (https://${MEDIA_DOMAIN}) — necessário porque a assinatura S3 inclui o host
# e o browser faz upload direto pra MEDIA_DOMAIN. Hairpin via DNS público é OK.
# Pra evitar hairpin, ajuste extra_hosts no compose pra resolver MEDIA_DOMAIN
# pra IP interno e set S3_INTERNAL_ENDPOINT=http://minio:9000 (avançado).
S3_INTERNAL_ENDPOINT=
# ----- App
COUPLE_NAMES=Stefanie & Leandro
EVENT_DATE=07 de junho de 2026
# ----- Admin (painel dos noivos)
ADMIN_PASSWORD=senha-forte-compartilhada-entre-os-dois
SESSION_SECRET=gere-um-uuid-longo-aqui-min-32-chars
ALLOWED_ADMIN_EMAILS=voce@exemplo.com,outro@exemplo.com
feat: HEIC->JPEG transcoding and Postgres + MinIO backup sidecars HEIC handling - pillow-heif joins the deps; app/lib/transcode.py registers the HEIF opener and exposes heic_to_jpeg(bytes, quality=88) with EXIF rotation applied so portrait iPhone photos do not show sideways. - Storage gains get_bytes / put_bytes so the server can read the uploaded HEIC out of MinIO, decode it, and put a JPEG back. - /api/uploads/{id}/confirm now runs the transcode after the HEAD check passes when mime_type is image/heic or image/heif: writes the JPEG under a sibling key, deletes the HEIC, and updates the upload row's storage_key / mime_type / size_bytes. Failures fall back to keeping the HEIC so an upload is never lost in transit; the admin can re-upload if a particular file is unrenderable. Backups (two sidecars in docker-compose.yml) - postgres-backup uses prodrigestivill/postgres-backup-local:16-alpine with BACKUP_SCHEDULE_DB (default @daily) and layered retention (days/weeks/months) writing to ./backups/postgres on the host. - media-backup is an alpine container that pulls mc on boot, sets up an alias for the in-cluster MinIO, optionally adds a remote alias (R2/B2/S3 via BACKUP_REMOTE_*), and runs mc mirror on a configurable cron schedule. Local mirror always; remote mirror only when BACKUP_REMOTE_* are set. - Both write to ./backups/ on the host (bind mount), so the operator can rsync the directory off-box without touching containers. - .env.example documents every new variable, including a R2 example for the remote target, and TZ for cron alignment. Local backups directory is .gitignore'd so accidental commits do not ship someone else's wedding photos to GitHub.
2026-06-07 19:50:29 -03:00
# ----- Backup (vai pra ./backups/ no host por padrão)
TZ=America/Sao_Paulo
# Cron schedule para o Postgres: aceita formato cron OR @daily/@hourly/etc
BACKUP_SCHEDULE_DB=@daily
# Cron para o MinIO (mc mirror é incremental, pode rodar mais vezes)
BACKUP_SCHEDULE_MEDIA=0 3 * * *
# Retenção (camadas: dias / semanas / meses) — só pro Postgres
BACKUP_KEEP_DAYS=14
BACKUP_KEEP_WEEKS=4
BACKUP_KEEP_MONTHS=6
# Backup remoto OPCIONAL — espelha o bucket pra outro provedor S3 (R2,
# B2, AWS S3, outro MinIO). Deixe vazio pra ficar só com backup local.
# Exemplo com Cloudflare R2:
# BACKUP_REMOTE_ENDPOINT=https://<account-id>.r2.cloudflarestorage.com
# BACKUP_REMOTE_ACCESS_KEY=...
# BACKUP_REMOTE_SECRET_KEY=...
# BACKUP_REMOTE_BUCKET=wedding-media-backup
BACKUP_REMOTE_ENDPOINT=
BACKUP_REMOTE_ACCESS_KEY=
BACKUP_REMOTE_SECRET_KEY=
BACKUP_REMOTE_BUCKET=
Reference in New Issue Copy Permalink