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.
Build an Angular application with the committed workspace configuration, serve its browser output, verify route fallback, and promote it to a managed HTTPS domain.
Candidate release
Angular
SOURCE
Git
REGION
de
ROUTE
HTTPS
01Source received
02Build completed
03Runtime started
04Health check passed
Promoted route
production.adios.run
A production path for
The production path
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.
Run the workspace's production build and keep configuration replacements, output paths, and dependency locks visible in source control.
Serve the browser build from a production process, test direct navigation to Angular routes, and promote only after the root check responds.
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
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.
Bring the existing repository, or inspect and deploy one of the exact starter variants linked below.
$adios loginKeep commands, runtime or service version, health behavior, and secret references in adios.yaml.
$git diff -- adios.yamlFollow build and runtime evidence, verify the candidate, and open the promoted route or service connection.
$adios upname: angular-app
build_cmd: npm ci && npm run build
start_cmd: npm start
runtime:
name: node@24
port: 3000
health_path: /Deployable starting points
Begin with the Nginx static starter, then replace its example files with the output from your Angular production build.
Web apps
An Nginx starter for static HTML, CSS, JavaScript, and single-page apps.
git clone https://github.com/adiosdotdev/templates.git
cd templates/nginx/static
adios upBefore production
The safest first release starts with a reproducible build or service configuration and a preview that exercises the dependencies production will actually use.
Questions, answered
Review the runtime or service boundary, template path, failure behavior, and production checks before creating the first release.
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.
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.
Yes. Build the browser application, serve the output directory, and configure history fallback so direct navigation reaches Angular instead of a static 404.
Deploy the server bundle as a persistent Node.js process and replace the static start command with the framework's production server command.
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.
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.
Related deployment paths
Publish HTML, CSS, JavaScript, or a framework-generated static build from a small Nginx starter with routes, domains, TLS, and release state attached.
Build a React application from its existing repository, serve the generated output or production Node.js process, and connect the release to a stable HTTPS route.
Build a Vue application from its existing repository, serve the production output, verify client-side routes, and promote it to a managed HTTPS domain.
Build a Svelte or SvelteKit project with its chosen adapter, serve the emitted output, verify routes, and keep the production command attached to source.
The first release
Start from the repository or a template, review the deployment contract, and inspect what becomes the promoted production version.