Timo Knuth
113acc073f
Groundwork for testmodul.qrmaster.net, a second stack running the `test` branch on a real qrmaster.net subdomain. Production scopes its session cookie to .qrmaster.net, so the browser sends it to every subdomain including staging. With both environments naming the cookie `userId`, the browser holds two cookies of the same name and cookies.get() picks one arbitrarily - staging logins would look randomly signed-out. AUTH_COOKIE_NAME lets staging pick `userId_test` instead. Production keeps the `userId` default; changing it there would invalidate every existing session. Wired getAuthCookieName() into the six places that named the cookie literally. The account deletion route now expires both the host-only and the domain-scoped variant like the logout route already does, instead of a single cookies().delete() that would leave the other one behind. NEXT_PUBLIC_WWW_URL and NEXT_PUBLIC_APP_URL become build ARGs so the same image can be built pointing at the staging host - the defaults keep a plain production build byte identical to before. Like COOKIE_DOMAIN these must exist at build time, because process.env is inlined into the Edge middleware bundle. robots.ts now serves Disallow-all unless NEXT_PUBLIC_INDEXABLE is true. Staging otherwise returns the production robots.txt and invites crawlers to index a duplicate of www. docker-compose.test.yml is the staging overlay. Two things it must get right, both verified against `docker compose config`: - db and redis need `networks: !override`. Compose MERGES the networks mapping from the base file, and since qrmaster-network is external and shared, a plain list left them attached to it - `db` would then resolve to two containers and staging could read and write the production database. - The web entrypoint is replaced so `prisma migrate deploy` never runs. prisma/migrations stopped in April 2026 and the schema has moved on through manual SQL since, so applying them to a fresh database would build a stale schema. Staging gets its schema from `pg_dump --schema-only` against production instead. Verified: tsc clean, production build succeeds, and the merged compose config confirms staging keeps db/redis off the shared network while production resolves unchanged. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
83 lines
3.0 KiB
Plaintext
83 lines
3.0 KiB
Plaintext
# Environment Configuration
|
|
NODE_ENV=development
|
|
PORT=3000
|
|
|
|
# Database Configuration (PostgreSQL)
|
|
POSTGRES_USER=postgres
|
|
POSTGRES_PASSWORD=postgres
|
|
POSTGRES_DB=qrmaster
|
|
|
|
# For local development (without Docker):
|
|
# DATABASE_URL=postgresql://postgres:postgres@localhost:5435/qrmaster?schema=public
|
|
# For Docker Compose (internal Docker network):
|
|
DATABASE_URL=postgresql://postgres:postgres@db:5432/qrmaster?schema=public
|
|
|
|
# NextAuth Configuration
|
|
NEXTAUTH_URL=http://localhost:3050
|
|
NEXTAUTH_SECRET=your-secret-key-here-change-in-production
|
|
|
|
# Session cookie scope. Leave EMPTY for local development (browsers reject dotted
|
|
# domains on localhost). In production set to `.qrmaster.net` so the session is shared
|
|
# between www.qrmaster.net and app.qrmaster.net. Only honoured when NODE_ENV=production.
|
|
COOKIE_DOMAIN=
|
|
|
|
# Name of the session cookie. Leave empty in production and development (defaults to
|
|
# `userId`). The staging deployment on testmodul.qrmaster.net must set its own name, e.g.
|
|
# `userId_test`: production scopes its cookie to .qrmaster.net, so the browser sends it to
|
|
# every subdomain, and two cookies with the same name make the lookup ambiguous.
|
|
# Changing this in production logs out every user.
|
|
AUTH_COOKIE_NAME=
|
|
|
|
# Host split: marketing/SEO on WWW, the logged-in app on APP. Keep both pointing at the
|
|
# same origin locally so nothing redirects across hosts in development.
|
|
# In production: NEXT_PUBLIC_WWW_URL=https://www.qrmaster.net
|
|
# NEXT_PUBLIC_APP_URL=https://app.qrmaster.net
|
|
# NEXT_PUBLIC_WWW_URL must stay on www - it is the origin encoded into downloaded QR
|
|
# codes and used for public links in emails.
|
|
NEXT_PUBLIC_WWW_URL=http://localhost:3050
|
|
NEXT_PUBLIC_APP_URL=http://localhost:3050
|
|
|
|
# OAuth Providers (Optional)
|
|
GOOGLE_CLIENT_ID=
|
|
GOOGLE_CLIENT_SECRET=
|
|
|
|
# Redis Configuration (Optional - for rate limiting and caching)
|
|
REDIS_URL=redis://redis:6379
|
|
|
|
# Security
|
|
# Used for hashing IP addresses in analytics
|
|
IP_SALT=your-ip-salt-here-change-in-production
|
|
|
|
# Features
|
|
ENABLE_DEMO=false
|
|
|
|
# SEO Configuration
|
|
# Set to 'true' in production to allow search engine indexing
|
|
NEXT_PUBLIC_INDEXABLE=true
|
|
|
|
# Stripe Payment Configuration (Optional - for subscription payments)
|
|
# Get your keys from: https://dashboard.stripe.com/apikeys
|
|
STRIPE_SECRET_KEY=
|
|
STRIPE_WEBHOOK_SECRET=
|
|
NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY=
|
|
|
|
# Stripe Price IDs (create these in your Stripe dashboard)
|
|
# NEXT_PUBLIC_STRIPE_FREE_PRICE_ID=price_xxx
|
|
# NEXT_PUBLIC_STRIPE_PRO_PRICE_ID=price_xxx
|
|
# NEXT_PUBLIC_STRIPE_BUSINESS_PRICE_ID=price_xxx
|
|
|
|
# Analytics (Optional - PostHog)
|
|
NEXT_PUBLIC_POSTHOG_KEY=
|
|
NEXT_PUBLIC_POSTHOG_HOST=https://app.posthog.com
|
|
|
|
# Analytics (Optional - Microsoft Clarity session recordings & heatmaps)
|
|
NEXT_PUBLIC_CLARITY_PROJECT_ID=
|
|
|
|
# TikTok Content Posting API (Hermes Agent automated posting)
|
|
TIKTOK_CLIENT_KEY=
|
|
TIKTOK_CLIENT_SECRET=
|
|
TIKTOK_REDIRECT_URI=https://qrmaster.net/api/tiktok/callback
|
|
# Optional: protects /api/tiktok/connect from being triggered by strangers
|
|
TIKTOK_ADMIN_KEY=
|
|
TIKTOK_EXPECTED_OPEN_ID=
|