viewport

Viewport — Split View Control

Every page is a split view: terminal on the left, viewport (iframe) on the right. Each session has its own viewport.

Push content to the viewport

Use push-view — it auto-detects your session. That's the only way to update what the user sees.

push-view /wolt/<name>/site/my-page.html

URL paths

Wolt sites are served at /wolt/<name>/site/:

• wolt/site/hello.html → /wolt/<name>/site/hello.html
• wolt/site/index.html → /wolt/<name>/site/ (index is served at the directory root)

A bare page.html (or wolt/site/page.html, or the file's path on disk) is turned into your site's path for you. push-view checks the page loads first: if it says "not found", the file isn't there yet, and nothing was shown.

The server runs on port 7777. You never need to curl it directly — push-view handles everything.

Live reload

Sites have automatic live reload. When you edit files in wolt/site/, the viewport updates immediately — no need to call push-view again after the initial push. Just edit and save.

App URLs

To push an app to the viewport, use the subdomain pattern:

push-view http://my-app.localhost:7777/

The format is http://<app-name>.localhost:7777/. Do not use /app/<name>/ — that path triggers a 302 redirect to the app's bare port, which breaks through the Cloudflare tunnel.

Tips

• The viewport only shows content served by localhost:7777. External URLs won't work (iframe CORS).
• Each session's viewport is independent. Pushing to one doesn't affect others.
• Always use push-view — never manually curl to /current.
• If you don't know your wolt name, check $WOLTSPACE_WOLT_NAME or read wolt/wolt.json.