Your first deployment

Install the CLI and log inCopy Anchor Link

curl -fsSL https://nitroship.co/install.sh | bash
ntro login

Create an appCopy Anchor Link

Move into the project folder you want to deploy and create an app.

cd my-project
ntro apps create hello-site

hello-site becomes the app's slug (the name used in its address), so production lives at https://hello-site.ntro.run. Leave the name out and the CLI suggests the folder name.

Creating an app links the current folder to it. The link is saved in .nitroship/app.json, so commands run in this folder know which app you mean without --app. Add --no-link if you do not want that.

DeployCopy Anchor Link

Deploy straight from the linked folder. --prod means "deploy to production".

ntro deploy . --prod

Your source goes to the remote builder, which installs dependencies and builds for you. It detects the project type automatically, checking for a Dockerfile, then Next.js, then framework presets, then plain static files. To pick a preset yourself, set build.framework in nitroship.json. It wins even over a root Dockerfile and can't be combined with build.dockerfile.

To upload only an already-built static folder, pass that folder. The app link lives in the current folder, not in subfolders like ./public, so name the app with --app.

ntro deploy ./public --app hello-site --prod

Check the resultCopy Anchor Link

ntro deploy waits until the build finishes (ready or failed) and then prints two addresses:

• Production URL hello-site.ntro.run: always shows the current production deployment.
• Revision URL hello-site-<short-id>.rev.ntro.run: pinned to the deployment you just made.

List your deployments with:

ntro deployments list