Deploy and Host

innovative-truth is a production-ready Next.js 14 template with i18n, Tailwind, and Supabase integration (Auth, DB, Storage). It’s designed for two modes: DIY (self-host the ZIP) and Fully-Managed (auto-provision a live site per customer on Railway). Connect your repo, set env vars, deploy, and scale without server config.

About Hosting

Hosting innovative-truth on Railway is straightforward. Create a Railway Template from the repo, then provision a fresh Railway project from that template for each customer. Railway builds via Nixpacks (or your Dockerfile), runs next start on the assigned PORT, and scales automatically. You’ll set environment variables at deploy time (Supabase URL and Anon Key, base URL, per-site identifiers), keeping secrets out of the repo. You can use Railway’s default domain or attach custom subdomains. This approach enables fully automated per-customer provisioning while maintaining a clean codebase and minimal operational overhead.

Why Deploy

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying innovative-truth on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.

Common Use Cases

Fully-managed, per-customer websites spun up from a single template Multilingual marketing/directory sites with Supabase-backed auth/forms SEO-focused landing pages that need quick global deployment and scaling

Dependencies for

Node.js 18+ runtime Next.js 14 with scripts: build: next build start: next start -p ${PORT} Recommended: Next.js standalone output for smaller runtime footprint Supabase project (URL + Anon Key) for auth/data/storage Required environment variables (set on Railway):

NEXT_PUBLIC_SUPABASE_URL NEXT_PUBLIC_SUPABASE_ANON_KEY NEXT_PUBLIC_BASE_URL SITE_ID (per‑site identifier) SITE_NAME (optional branding) Optional: NEXT_PUBLIC_DEFAULT_LOCALE, NEXT_PUBLIC_SUPPORTED_LOCALES Example package.json scripts:

json { "scripts": { "build": "next build", "start": "next start -p ${PORT}" }, "engines": { "node": ">=18" } } Recommended next.config.js:

js /** @type {import('next').NextConfig} / const nextConfig = { output: 'standalone', images: { remotePatterns: [ { protocol: 'https', hostname: '.supabase.co' } ], }, } module.exports = nextConfig

Deployment Dependencies

Railway Templates: https://docs.railway.app/deploy/deployments#templates Environment Variables: https://docs.railway.app/guides/variables Nixpacks (Node): https://nixpacks.com/docs/providers/node Custom Domains: https://docs.railway.app/guides/custom-domains Next.js Standalone: https://nextjs.org/docs/app/building-your-application/deploying#standalone-mode Supabase API Keys: https://supabase.com/docs/guides/api#api-keys If you want, I can turn this into a README snippet in your template repo or adjust wording to match your brand voice.