Skip to content
OrbixPanel OrbixPanel Tutorials

Deploy a Nuxt (Vue) app on OrbixPanel

Nuxt 3 can run two ways, and OrbixPanel supports both. Pick based on whether you need server-side rendering.

Static (pre-rendered)

nuxt generate pre-renders your site to static files in .output/public. Point your build script at it:

{ "scripts": { "build": "nuxt generate" } }

OrbixPanel builds it and serves the static output with nginx — the static site path. Great for content sites and marketing pages.

SSR (Node server)

nuxt build produces a Nitro Node server at .output/server/index.mjs. OrbixPanel serves a project as a managed Node process when it has a start script, so add one:

{
  "scripts": {
    "build": "nuxt build",
    "start": "node .output/server/index.mjs"
  }
}

Nitro listens on the PORT environment variable, which OrbixPanel sets — so SSR, server routes (/server/api), and dynamic rendering all work with no extra config.

Deploy either way

  1. Push to Git → Apps → Deploy from Git → repo + branch → Deploy.
  2. Add your domain + SSL.

Which should I pick?

Static (nuxt generate)SSR (nuxt build)
SpeedFastest (files)Fast (rendered per request)
Server routes / dynamic dataNoYes
Resource useMinimalA running process

For a mostly-content site, generate. For dashboards or per-request data, SSR. See how deploys work for the detection rules.

Running OrbixPanel? Nuxt deploys static or SSR, straight from Git. OrbixPanel.com → — the free, self-hosted, AI-powered hosting control panel.