Apps should not autostart on deploy #55

New issue

Closed

opened 2026-06-09 15:38:51 +00:00 by Mark · 0 comments

Mark commented

2026-06-09 15:38:51 +00:00

Owner

When deploying an app via Node Hub (API or UI), the app should be staged only — not automatically started. The deploy flow should clone, validate, build the image, and store the container definition, but not actually run the container until the user explicitly requests it.

This prevents resource waste from apps that deploy but arent ready for traffic yet, and gives the user a chance to verify before the app goes live.

Requirements:

Deploy → stage only (image built, metadata saved, container NOT started)
Separate start/stop actions to run a staged app
UI should show staged vs running state clearly

There is already a stageApp / startStagedApp pattern in NodeAppLauncher.js — the deploy endpoint needs to use it instead of calling launchFromRepository directly.

When deploying an app via Node Hub (API or UI), the app should be **staged** only — not automatically started. The deploy flow should clone, validate, build the image, and store the container definition, but not actually run the container until the user explicitly requests it. This prevents resource waste from apps that deploy but arent ready for traffic yet, and gives the user a chance to verify before the app goes live. **Requirements:** - Deploy → stage only (image built, metadata saved, container NOT started) - Separate start/stop actions to run a staged app - UI should show staged vs running state clearly There is already a `stageApp` / `startStagedApp` pattern in NodeAppLauncher.js — the deploy endpoint needs to use it instead of calling launchFromRepository directly.