Adios
Frontend apps · plans from $10/month

Deploy Vue.Publish the built site.

Build a Vue application from its existing repository, serve the production output, verify client-side routes, and promote it to a managed HTTPS domain.

Keep the repositoryInspect build and logsCustom domains and TLS
Adios deploy

Candidate release

Vue

Healthy

SOURCE

Git

REGION

de

ROUTE

HTTPS

01Source received

02Build completed

03Runtime started

04Health check passed

Promoted route

production.adios.run

A production path for

VueViteStatic outputSPA routingCustom domains

The production path

A working Vue project still needs a safe release.

The application or service is only one part of production. Build evidence, runtime state, health, secrets, logs, routes, and the promoted version should remain inspectable together.

Keep the Vue build you already use

Use npm ci and the project's normal Vue or Vite build. Keep the output directory, base URL, and environment-variable behavior explicit.

Promote the version that reports healthy

Serve the built assets with a production process, verify the root and nested client routes, and promote after the configured check responds.

Trace production back to source

Build output, runtime logs, health state, secrets, domains, and the promoted release stay attached to the project instead of being split across unrelated tools.

From source to release

Three steps keep the deployment path reviewable.

Use the source and production behavior the project already has. The manifest records what the platform should build or provision and how the result becomes ready.

  1. 01

    Start with source or a template

    Bring the existing repository, or inspect and deploy one of the exact starter variants linked below.

    $adios login
  2. 02

    Review the deployment contract

    Keep commands, runtime or service version, health behavior, and secret references in adios.yaml.

    $git diff -- adios.yaml
  3. 03

    Deploy and inspect the result

    Follow build and runtime evidence, verify the candidate, and open the promoted route or service connection.

    $adios up
adios.yaml
Your project
name: vue-app
build_cmd: npm ci && npm run build
start_cmd: npm start

runtime:
  name: node@24
  port: 3000
  health_path: /
Configure npm start to serve the production dist directory, or use the Nginx static template as the starting point.

Deployable starting points

Start Vue from a template when the repository is not ready.

The Nginx static starter provides a small production serving path that you can replace with the output from a Vue build.

Web apps

Nginx Static

An Nginx starter for static HTML, CSS, JavaScript, and single-page apps.

HTMLNone
Template key
nginx:static
Runtime
nginx
Repository
templates
Source path
nginx/static
git clone https://github.com/adiosdotdev/templates.git
cd templates/nginx/static
adios up

Before production

Verify the workload.Then promote it.

The safest first release starts with a reproducible build or service configuration and a preview that exercises the dependencies production will actually use.

Ready when…

  • The production build emits the expected dist directory.
  • Nested browser routes return the application shell.
  • Asset URLs work on the generated and custom domains.
  • Secrets are not compiled into client JavaScript.

Preview when…

  • The app uses Nuxt or another server-rendered runtime.
  • The router assumes a non-root deployment base.
  • Environment variables differ between build and runtime.

Questions, answered

What to know before deploying Vue.

Review the runtime or service boundary, template path, failure behavior, and production checks before creating the first release.

Can Adios deploy an existing Vue project?

Yes. Run the Adios CLI from the project root, keep the repository and dependency files you already use, and add an adios.yaml file that describes the production build, start command, port, and health path.

Do I need Docker to deploy Vue?

Not for a standard supported runtime. Use the project's normal production commands in adios.yaml. If the build needs unusual operating-system packages or native libraries, verify those dependencies in a preview before promotion.

Can Adios deploy a Vue app built with Vite?

Yes. Build the project with its locked dependencies and serve the generated dist directory with a production static process.

How do Vue Router history routes work in production?

Configure the static server to return the application shell for browser routes that do not map to files, then verify direct navigation in a preview.

What happens when the build or health check fails?

The candidate release keeps its build and runtime output for inspection. It must report healthy before it becomes the promoted version serving the application route.

Can I start from a template instead of an existing repo?

Yes. This page links to the closest official Adios Vue starters. Inspect the exact source variant, deploy it in the console, or clone it locally and run adios up.

The first release

Deploy Vue with the source and evidence attached.

Start from the repository or a template, review the deployment contract, and inspect what becomes the promoted production version.