Deploy Angular

How nesly detects, builds and serves a Angular project — and the two commands that put it on a live URL.

Deploy Angular on nesly

A Angular project is built once and served as static files — no server process to keep alive.

cd your-project
nesly deploy --yes

The first deploy creates the project and prints the live URL; after that,nesly deploy is enough.

How detection sees it

A package.json depending on @angular/cli or @angular/core is detected as Angular.
The output directory is read from angular.json (outputPath); Angular 17+ putting the browser bundle one directory deeper is handled.

When detection is not what you want, say it yourself: build and start commands, root directory and output directory live in nesly.tomlcommitted next to the code — see builds.

Worth knowing

Keep angular.json's outputPath accurate — it is the single source the platform reads.
When a deploy fails, nesly diagnosereads the logs for you and names the fix.

Full walkthrough: get started. Custom domains, backups, GitHub deploys and the rest of the reference: nesly CLI.