Dokploy & environment

Principles

• Set runtime secrets only in the deployment UI or sealed env — never commit real keys.
• Typical keys include: DATABASE_URL, AUTH_SECRET, AUTH_URL, NEXT_PUBLIC_WEB_URL, optional CRON_SECRET_KEY, VAPID keys for push, etc.

Dokploy workflow

1. Open your project → application → Environment / Variables.
2. Add or update variables, then Save and Redeploy / Restart so the process picks them up.
3. Confirm in logs that Next.js booted and env is loaded.

Cron secret naming

Application code expects CRON_SECRET_KEY for /api/cron/* auth. If your panel used a different name (e.g. CRON_SECRET), align the name with what process.env reads in src/app/api/cron/*/route.ts.

Fidelity

When deployment requirements change, update this page and status/changelog.

Dependencies

Environment (representative checklist for the whole app — configure in the host UI)

• DATABASE_URL — PostgreSQL.
• AUTH_SECRET, and the callback base URL your Auth setup expects (align with OAuth).
• NEXT_PUBLIC_WEB_URL — site origin for redirects (checkout, callbacks).
• CRON_SECRET_KEY — Cron Bearer for external schedulers.
• ADMIN_EMAILS, NEXT_PUBLIC_ADMIN_EMAILS — Admin allowlist.
• Payments: PAY_PROVIDER, STRIPE_PRIVATE_KEY, STRIPE_WEBHOOK_SECRET, CREEM_API_KEY, CREEM_WEBHOOK_SECRET, CREEM_PRODUCTS, CREEM_ENV, NEXT_PUBLIC_PROJECT_NAME, NEXT_PUBLIC_PAY_CANCEL_URL.
• Push: NEXT_PUBLIC_VAPID_PUBLIC_KEY, VAPID_PRIVATE_KEY, VAPID_SUBJECT — Notifications.
• Web3: NEXT_PUBLIC_WEB3_ENABLED, NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID, NEXT_PUBLIC_SUPPORTED_CHAINS, NEXT_PUBLIC_WEB3_APP_URL — Web3 auth.

Database

• Entire schema in src/db/schema.ts — single Postgres; no Dokploy-specific tables.