Developer Workflows & Framework Guides

Practical, step-by-step guides for common application deployment workflows.

---

1. Deploying a Next.js Application

Aureon provides first-class support for Next.js applications (both Pages Router and App Router):

1. Ensure your package.json contains standard scripts:

   "scripts": {
     "dev": "next dev",
     "build": "next build",
     "start": "next start"
   }

2. Connect your GitHub repository in the Aureon console.
3. Aureon detects Next.js automatically and configures output directory and build command.
4. Add required environment variables (e.g. DATABASE_URL).
5. Click Deploy. SSR routes, API endpoints, and static pages will be provisioned seamlessly.

2. Deploying a React or Vite Application

For client-side single-page applications built with React, Vite, or Create React App:

1. Confirm your build command is configured (e.g. vite build) and outputs to dist or build.
2. Aureon automatically serves static assets with global CDN caching and configures SPA fallback routing so deep links resolve cleanly.

3. Deploying a Node.js Web Server

For custom backend services built with Express, Fastify, or standard Node.js:

1. Ensure your server binds to 0.0.0.0 and uses process.env.PORT:

   const port = process.env.PORT || 3000;
   app.listen(port, '0.0.0.0', () => {
     console.log(`Server running on port ${port}`);
   });

2. Confirm your package.json includes a start script: "start": "node server.js".
3. Aureon provisions a dedicated container that boots your server automatically.

4. Deploying a Static Website

For plain HTML, CSS, JavaScript, and static asset sites:

1. Place your files in your repository root (or a designated subfolder).
2. Aureon serves your files directly via global edge points of presence with instant cache invalidation on new deployments.

5. Rolling Back a Deployment

To revert to an earlier deployment version:

1. Go to Deployments in your project dashboard.
2. Find the previous working build.
3. Click the options menu and select Promote to Production.
4. Edge routing immediately points production traffic to the verified build.