Deploying full-stack applications on EGREED Deploy

Overview

This guide walks through deploying Full-stack (React + Node, Next.js, Nuxt, Remix) applications on EGREED Deploy. You'll go from a working local project to a live production URL with automated Git deploys, environment variables, and a custom domain.

Requirements

• An EGREED account (create one at deploy.egreedtech.org)
• A working Full-stack (React + Node, Next.js, Nuxt, Remix) project committed to GitHub, GitLab, or Bitbucket
• Node.js 20+ (or Python 3.11+ for Python projects) locally to test the build

Step-by-step guide

1. Log in to EGREED Deploy and click New Project.
2. Choose Import from Git and pick your Full-stack (React + Node, Next.js, Nuxt, Remix) repository.
3. EGREED Deploy auto-detects Full-stack (React + Node, Next.js, Nuxt, Remix). Confirm the following defaults:
   • Install command: npm install
   • Build command: npm run build
   • Output directory: .output or dist
4. Add environment variables (e.g. DATABASE_URL, API keys) under Environment.
5. Click Deploy. EGREED Deploy installs, builds, and publishes to a live URL.
6. Optional: attach a custom domain from Domains.

Configuration

Add a egreed.json or egreed.yaml to your repo to version-control build settings, headers, redirects, and rewrites. Example headers:

{
  "framework": "Full-stack (React + Node, Next.js, Nuxt, Remix)",
  "build": "npm run build",
  "output": ".output or dist",
  "headers": [{ "source": "/(.*)", "headers": [{ "key": "X-Frame-Options", "value": "DENY" }] }]
}

Common errors

• Build failed: dependency not found. Ensure all dependencies are in package.json (or requirements.txt) and committed.
• Missing environment variable. Add missing keys under Environment → Production.
• Output directory not found. Verify the build command actually produces .output or dist.

Troubleshooting

Open Deployments → Logs to see full build and runtime output. Reproduce locally with the same Node/Python version. Contact support at [email protected] if a deploy remains stuck.