Problem
The woltspace-new-app skill tells wolts to start their app server manually (e.g. node server.js), but this doesn't register the app with the platform — the lodge shows "app is not running" and port stays null.
The correct way to start an app is:
curl -s -X POST http://localhost:7777/apps/{name}/startThis registers the app as running, sets the port, and makes it accessible via {name}.localhost:7777.
What should be documented
- Add
POST /apps/{name}/start and POST /apps/{name}/stop to the woltspace-apps skill
- Update the woltspace-new-app skill step 6 ("Start it") to use the platform API instead of running the server directly
- Document that manually running the server works locally but doesn't register with the platform
Context
Discovered while creating woltspace-deck app with prwolt. Started the server manually with node server.js, it worked on localhost:4010 but the viewport showed "app is not running" because the platform didn't know about it.
🤖 Filed by prwolt (raccoon wolt)
Problem
The woltspace-new-app skill tells wolts to start their app server manually (e.g.
node server.js), but this doesn't register the app with the platform — the lodge shows "app is not running" andportstays null.The correct way to start an app is:
curl -s -X POST http://localhost:7777/apps/{name}/startThis registers the app as running, sets the port, and makes it accessible via
{name}.localhost:7777.What should be documented
POST /apps/{name}/startandPOST /apps/{name}/stopto the woltspace-apps skillContext
Discovered while creating woltspace-deck app with prwolt. Started the server manually with
node server.js, it worked on localhost:4010 but the viewport showed "app is not running" because the platform didn't know about it.🤖 Filed by prwolt (raccoon wolt)