# Deploy a Nuxt Site on FlyWP Through Git

> Configure and deploy Nuxt on FlyWP using a Nitro Node server or generated static pages.

Source: https://flywp.com/docs/site/nodejs-sites/nuxt/

Deploy a Nuxt application from a Git repository using FlyWP's JavaScript site wizard. This guide uses the modern Nuxt/Nitro workflow; legacy Nuxt 2 projects need their own compatibility and deployment review.

See the [shared Git deployment guide](https://flywp.com/docs/site/nodejs-sites/) for provider access, DNS, and release management.

## Before you begin

You need an active FlyWP-managed server, a connected Git provider, and an application with `package.json` at the repository root. Monorepos are excluded by the current wizard. Commit source, configuration, and the lockfile, then test a production build locally.

Declare a Node major compatible with your Nuxt release and dependencies. For example, use `"engines": { "node": "22.x" }` if Node.js 22 is supported by your project.

## Choose your deployment mode

Use Server for request-time rendering, private server operations, and Nitro API endpoints. Use Static when all required pages can be generated or served as a client-side application with an external backend.

A Nuxt Node build has a server entrypoint at `.output/server/index.mjs`. A generated static site is served from `.output/public`. Merely disabling SSR does not replace the generation step. [Nuxt deployment guide](https://nuxt.com/docs/4.x/getting-started/deployment).

## Option A: Prepare a Server application

Merge these scripts into `package.json`:

```json
{
  "scripts": {
    "build": "nuxt build",
    "generate": "nuxt generate",
    "start": "node .output/server/index.mjs"
  },
  "engines": {
    "node": "22.x"
  }
}
```

Keep your existing Nuxt dependencies and any installation lifecycle scripts. Make sure the build targets a Node server rather than a provider-specific edge preset. For Nuxt versions using this Nitro preset spelling, merge the following into `nuxt.config.ts`:

```ts
export default defineNuxtConfig({
  nitro: {
    preset: 'node-server',
  },
});
```

Use the preset name supported by your installed Nitro version; current standalone Nitro documentation uses `node_server`. The essential check is that your build emits a runnable `.output/server/index.mjs`. [Nuxt deployment presets](https://nuxt.com/docs/4.x/getting-started/deployment), [Nitro Node runtime](https://nitro.build/deploy/runtimes/node).

Test in your local development checkout:

```bash
npm ci
npm run build
node .output/server/index.mjs
```

Open the reported local address, check a page and a server endpoint, and stop the process afterward. The local test proves your repository builds and starts; it does not verify the FlyWP deployment.

## Option B: Prepare a Static application

Use the `generate` script above, then run:

```bash
npm ci
npm run generate
```

Inspect `.output/public` and preview it with a local static server. Make sure your required routes are generated; add routes to the prerender configuration when they cannot be discovered automatically. A client-only app can use `ssr: false`, but still needs generation and a tested fallback for direct navigation. [Nuxt prerendering documentation](https://nuxt.com/docs/3.x/getting-started/prerendering).

Static hosting does not run the application's Nitro API routes. Use an external API or Server runtime for backend functionality. Any build-time content must be available while generation runs.

<figure>
  <a
    href="https://flywp.com/images/docs/nodejs-sites/site-type.jpg"
    target="_blank"
    rel="noopener noreferrer"
    aria-label="Open full-size screenshot: FlyWP Create Site dialog with the Node.js Next.js Nuxt Astro choice"
  >
    <img
      src="https://flywp.com/images/docs/nodejs-sites/site-type.jpg"
      alt="FlyWP Create Site dialog with the Node.js Next.js Nuxt Astro choice"
      width="1280"
      height="1063"
      loading="lazy"
    />
  </a>
  <figcaption>
    Open the JavaScript site wizard from the application selector. Select the image to view the full screen.
  </figcaption>
</figure>

## Create the site in FlyWP

1. Sign in to [FlyWP](https://app.flywp.com).
2. Follow **Dashboard → New Site → Select Server → Continue → Node.js Next.js / Nuxt / Astro**.
3. On **Domain**, use the test-domain switch or enter a custom **Domain Name** and configure the available DNS/HTTPS options. Click **Next**.
4. On **Configure Git**, select **Nuxt**, choose your runtime, and configure these values.

| Field            | Server                          | Static generation                                       |
| ---------------- | ------------------------------- | ------------------------------------------------------- |
| Application Type | Nuxt                            | Nuxt                                                    |
| Runtime          | Server                          | Static                                                  |
| Package manager  | npm                             | npm                                                     |
| Build command    | `npm run build`                 | `npm run generate`                                      |
| Start command    | `node .output/server/index.mjs` | Hidden; no Node process                                 |
| Web directory    | `/` — observed default          | `/.output/public` — proposed mapping to generated files |

The inspected wizard retained `npm run build` and `/` when switching Nuxt to Static. Change both explicitly for the generation workflow. The Static web directory mapping above must be checked in a real deployment. Use equivalent yarn or pnpm commands if you choose a different package manager.

5. Select the provider, **Repository**, and **Branch**. For a public repository missing from the list, type `owner/repository` and select the public repository option.
6. Choose whether to enable **Push to deploy**.
7. Click **Next** and complete **Installation**. In the inspected test-domain flow, this asks for **Site Title**.
8. Review **Summary**, paying particular attention to runtime, commands, directory, and branch. Click **Create Site** when ready.

<figure>
  <a
    href="https://flywp.com/images/docs/nodejs-sites/nuxt-server.jpg"
    target="_blank"
    rel="noopener noreferrer"
    aria-label="Open full-size screenshot: FlyWP Configure Git with Nuxt and Server selected and production build and start commands visible"
  >
    <img
      src="https://flywp.com/images/docs/nodejs-sites/nuxt-server.jpg"
      alt="FlyWP Configure Git with Nuxt and Server selected and production build and start commands visible"
      width="1280"
      height="2157"
      loading="lazy"
    />
  </a>
  <figcaption>
    Nuxt Server setup in the actual FlyWP app. Repository and branch remain to be selected. Select the image to view the
    full screen.
  </figcaption>
</figure>

<figure>
  <a
    href="https://flywp.com/images/docs/nodejs-sites/nuxt-static.jpg"
    target="_blank"
    rel="noopener noreferrer"
    aria-label="Open full-size screenshot: FlyWP Configure Git with Nuxt and Static selected and its build command and web directory visible"
  >
    <img
      src="https://flywp.com/images/docs/nodejs-sites/nuxt-static.jpg"
      alt="FlyWP Configure Git with Nuxt and Static selected and its build command and web directory visible"
      width="1280"
      height="2045"
      loading="lazy"
    />
  </a>
  <figcaption>
    Nuxt Static configuration example entered in the real wizard. These settings were not deployed. Select the image to
    view the full screen.
  </figcaption>
</figure>

## Configure runtime values

Declare application settings in `runtimeConfig`. Keep credentials outside its `public` section:

```ts
export default defineNuxtConfig({
  runtimeConfig: {
    apiSecret: '',
    public: {
      apiBase: '',
    },
  },
});
```

Merge this with your existing configuration and Nitro settings. Matching variables can override the declared values:

```dotenv
NUXT_API_SECRET=<private-api-secret>
NUXT_PUBLIC_API_BASE=https://api.example.com
```

Read them with `useRuntimeConfig()`. Values under `public` are available to browser code. [Nuxt runtime configuration](https://nuxt.com/docs/4.x/guide/going-further/runtime-config).

The production Node entrypoint does not automatically load your local `.env` file. Supply production values through the site's actual environment mechanism. Static generation requires relevant values during the build and has no Nuxt application process afterward. [Nuxt environment behavior](https://nuxt.com/docs/3.x/api/composables/use-runtime-config).

Nitro supports `NITRO_HOST`/`HOST` and `NITRO_PORT`/`PORT`, with port 3000 as its documented default. Match the interface and port to FlyWP's upstream configuration rather than arbitrarily changing the production port. [Nitro Node runtime](https://nitro.build/deploy/runtimes/node).

## Verify and update

Read the deployment logs, then test the hostname in a signed-out browser. Check assets, hydration, direct nested URLs, and any login or API workflow. A Server site should exercise a server endpoint; a Static site should work without the Nitro process.

Push updates to the configured branch. For automatic deployment, verify that **Push to deploy** is enabled and review the resulting release. Recover source changes with a new revert commit; database or external service changes require separate recovery.

## Troubleshooting

| Symptom                            | Action                                                                |
| ---------------------------------- | --------------------------------------------------------------------- |
| Missing `.output/server/index.mjs` | Inspect the failed build or an incompatible deployment preset         |
| Static site has no pages           | Use `nuxt generate`, then verify `.output/public` and Web directory   |
| Generated route is missing         | Add the route to prerender configuration and rebuild                  |
| `/api/...` fails on Static         | Move backend operations to an external service or use Server          |
| Secret/config value is empty       | Check declared runtime keys and matching production `NUXT_` variables |
| 502                                | Check process startup, host binding, and upstream port                |
| Client-only route fails on refresh | Verify Nginx's fallback behavior or prerender the required route      |

## Related guides

- [Next.js, Nuxt & Astro Site Support Through Git](https://flywp.com/docs/site/nodejs-sites/)
- [Deploy a Next.js Site on FlyWP Through Git](https://flywp.com/docs/site/nodejs-sites/nextjs/)
- [Deploy an Astro Site on FlyWP Through Git](https://flywp.com/docs/site/nodejs-sites/astro/)