Apps
List, inspect, deploy, redeploy, and open a shell for applications.
List applications
nextune app listExample:
NAME STATUS SOURCE ID
my-api RUNNING docker 9b1deb4d-3b7d-4bad-9bdd-2b0d7b3dcb6dUse --json for structured output.
Application details
nextune app get my-api
# or by ID
nextune app get 9b1deb4d-3b7d-4bad-9bdd-2b0d7b3dcb6dEdit application settings
Update configuration details for an existing application. You can modify the application name, container port, Docker image, image tag, or the deployment package plan.
nextune app edit my-apiIf you run this command without flags, it will open an interactive menu allowing you to select and edit individual fields.
Alternatively, you can provide flags to apply changes immediately:
nextune app edit my-api \
--name new-api-name \
--port 8080 \
--image nginx \
--tag 1.25 \
--package YOUR_PACKAGE_ID| Flag | Description |
|---|---|
--name | New application display name |
--port | Container port to expose |
--image | New Docker image name |
--tag | New Docker image tag |
--package | New deployment package ID |
Note: Updating these settings may require a redeploy for the changes to take effect.
Deploy from Docker image
Deploy a new application from a public or private registry image:
nextune app deploy \
--image nginx \
--tag latest \
--port 80 \
--package YOUR_PACKAGE_ID \
--name my-site \
--env NODE_ENV=production \
--env PORT=80| Flag | Required | Description |
|---|---|---|
--image | Yes | Docker image name |
--package | Yes | Deployment package ID from nextune packages list |
--tag | No | Image tag (default: latest) |
--name | No | Application display name |
--port | No | Container port to expose |
--env | No | Environment variables (KEY=VALUE) |
The CLI asks for confirmation unless you pass -y / --yes.
Deploy from GitHub
Deploy from a connected GitHub repository. You pass the repo; the CLI asks you to pick which GitHub account to use (you never type an integration ID).
Connect GitHub in the dashboard first if you have not already.
nextune app deploy \
--repo owner/my-app \
--branch main \
--package YOUR_PACKAGE_ID \
--name my-app \
--port 8080 \
--env NODE_ENV=production| Flag | Required | Description |
|---|---|---|
--repo | Yes | Repository as owner/name |
--package | Yes | Deployment package ID from nextune packages list |
--branch | No | Git branch (default: main) |
--dockerfile | No | Dockerfile path (default: Dockerfile) |
--build-type | No | DOCKERFILE (default) or AUTO |
--name | No | Application display name |
--port | No | Container port to expose |
--env | No | Environment variables (KEY=VALUE) |
Use either --repo or --image, not both. Confirmation is required unless -y / --yes is set.
Open a terminal
Open an interactive shell in a running application instance. It behaves like a normal local terminal.
nextune app terminal
# or by name / ID
nextune app terminal my-api
nextune app terminal --app-id 9b1deb4d-3b7d-4bad-9bdd-2b0d7b3dcb6d- If the app has one running instance, it connects automatically.
- If there are multiple instances, you pick which one to use.
- Optional:
--pod INSTANCE_NAMEto attach to a specific instance.
Press Ctrl+D or exit the shell to disconnect.
Redeploy
Restart an existing application (brief downtime possible):
nextune app redeploy my-apiConfirmation is required unless -y is set.
Related
- Environment Variables — manage application variables
- Logs — stream application logs
- Packages — find deployment package IDs