Auto-start apps when pushed to viewport
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 1
- Avg merge
- 7h 13m
- Merged PRs (30d)
- 31
Description
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:7777gets 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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace the subdomain-routing entry point and the push-view flow described in the issue, then reproduce the blank page with an app that is not running. Determine where either path can detect the app state and start it before serving the request. Done means opening an app through its subdomain or push-view works without a separate start request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100