Problem
When an app isn't running and you open it in the viewport (via push-view or navigating to <app>.localhost:7777/), you get a blank page or error. You have to manually start the app first with curl -s -X POST http://localhost:7777/apps/<name>/start.
Proposal
The platform should auto-start an app when it's requested but not running. Two places this could hook in:
- Subdomain routing — when
<app>.localhost:7777 gets a request and the app isn't running, start it before proxying
push-view — when pushing an app URL to the viewport, detect it's an app subdomain and start it if needed
Either way, the user/wolt shouldn't have to remember to start the app separately.
Context
This came up during the woltspace-deck presentation workflow — opened the viewport and got nothing because the app wasn't running yet.
Problem
When an app isn't running and you open it in the viewport (via
push-viewor navigating to<app>.localhost:7777/), you get a blank page or error. You have to manually start the app first withcurl -s -X POST http://localhost:7777/apps/<name>/start.Proposal
The platform should auto-start an app when it's requested but not running. Two places this could hook in:
<app>.localhost:7777gets a request and the app isn't running, start it before proxyingpush-view— when pushing an app URL to the viewport, detect it's an app subdomain and start it if neededEither way, the user/wolt shouldn't have to remember to start the app separately.
Context
This came up during the woltspace-deck presentation workflow — opened the viewport and got nothing because the app wasn't running yet.