Adios
Frontend apps · plans from $10/month

Deploy Angular.Publish the built site.

Build an Angular application with the committed workspace configuration, serve its browser output, verify route fallback, and promote it to a managed HTTPS domain.

Keep the repositoryInspect build and logsCustom domains and TLS
Adios deploy

Candidate release

Angular

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

AngularTypeScriptStatic outputSPA routingCustom domains

The production path

A working Angular 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 Angular build you already use

Run the workspace's production build and keep configuration replacements, output paths, and dependency locks visible in source control.

Promote the version that reports healthy

Serve the browser build from a production process, test direct navigation to Angular routes, and promote only after the root 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: angular-app
build_cmd: npm ci && npm run build
start_cmd: npm start

runtime:
  name: node@24
  port: 3000
  health_path: /
Set npm start to serve the Angular browser output and configure a fallback for client-side routes.

Deployable starting points

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

Begin with the Nginx static starter, then replace its example files with the output from your Angular production 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 configuration builds from a clean checkout.
  • The correct browser output directory is served.
  • Deep links fall back to index.html.
  • No private value is embedded in the browser bundle.

Preview when…

  • The project enables Angular server-side rendering.
  • Configuration replacements point at production services.
  • The app assumes a particular base href.

Questions, answered

What to know before deploying Angular.

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

Can Adios deploy an existing Angular 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 Angular?

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 I deploy an Angular single-page application?

Yes. Build the browser application, serve the output directory, and configure history fallback so direct navigation reaches Angular instead of a static 404.

What if the Angular project uses server-side rendering?

Deploy the server bundle as a persistent Node.js process and replace the static start command with the framework's production server command.

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 Angular starters. Inspect the exact source variant, deploy it in the console, or clone it locally and run adios up.

The first release

Deploy Angular 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.