Deploy Astro

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

Deploy Astro on nesly

A Astro project is served statically or run as a server, depending on how the project is configured.

nesly new astro-static my-app
cd my-app
nesly deploy --yes

The first deploy creates the project and prints the live URL; after that, nesly deploy is enough. The astro-static template is a complete, readable starting point.

How detection sees it

A package.json depending on astro is detected as Astro.
Without a server adapter the build output (dist/) is served as static files. With @astrojs/node (or another server adapter) the project runs as a container instead.

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

Worth knowing

If you add an adapter for SSR, the app must listen on the PORT the platform provides and bind 0.0.0.0.
Attach a managed database with nesly addon add postgres (or mssql) — connection env vars are injected on the next deploy.
When a deploy fails, nesly diagnose reads 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.