Poge is a Next.js 16 application that can be deployed to any platform supporting Node.js. Since all data is stored client-side in the browser, no database or backend configuration is required.Documentation Index
Fetch the complete documentation index at: https://docs.poge.dev/llms.txt
Use this file to discover all available pages before exploring further.
Deploy to Vercel (Recommended)
The fastest way to deploy Poge is using Vercel’s one-click deployment:Click the Deploy button
Click the “Deploy to Vercel” button above. You’ll be prompted to sign in to Vercel if you haven’t already.
Manual Vercel Deployment
If you prefer to deploy manually:Deploy to Netlify
Netlify supports Next.js applications with their Next.js Runtime:Connect your repository
- Log in to Netlify
- Click “Add new site” → “Import an existing project”
- Connect your Git provider and select your Poge repository
Configure build settings
Use these build settings:
- Build command:
npm run build - Publish directory:
.next - Functions directory: Leave empty
Netlify CLI Deployment
Deploy to Railway
Railway provides a simple deployment experience for Next.js applications:Create a new project
- Log in to Railway
- Click “New Project” → “Deploy from GitHub repo”
- Select your Poge repository
Configure deployment
Railway automatically detects Next.js and configures the build:
- Build command:
npm run build - Start command:
npm run start
Self-Hosted Deployment
Prerequisites
- Node.js 18.17 or later
- npm, pnpm, or yarn package manager
- A server with at least 512MB RAM
- SSL certificate (recommended for production)
Docker Deployment
Traditional Server Deployment
Start the production server
http://localhost:3000Environment Requirements
Node.js Version
Poge requires Node.js 18.17 or later. The application uses Next.js 16.1.5, which requires:- Node.js 18.17 or later
- React 19
Runtime Dependencies
Key dependencies that affect deployment:next: 16.1.5react: ^19pg: ^8.16.3 (for PostgreSQL connections)
Build Settings
The following build settings are configured innext.config.mjs:
- ESLint checks are skipped during builds (
ignoreDuringBuilds: true) - TypeScript errors are ignored during builds (
ignoreBuildErrors: true) - Image optimization is disabled (
unoptimized: true)
Port Configuration
By default, Poge runs on port 3000. You can change this by setting thePORT environment variable:
Reverse Proxy Configuration
For production deployments, use a reverse proxy like Nginx or Caddy:Post-Deployment Checklist
Enable HTTPS/SSL for secure database connections
Configure CORS if accessing from multiple domains
Set up monitoring and logging
Test database connectivity from the deployed instance
Verify that client-side storage (LocalStorage) is working correctly
Remember that Poge stores all data client-side. Each user’s data is stored in their browser’s LocalStorage, so no server-side data persistence is required.