Web app

Every daemon can serve the full app to a browser. There is no hosted frogg web app; you open your own daemon’s address.

Turn it on

Daemons installed with install.sh, Docker, Nix or frogg install-service already serve it. For a daemon you start by hand:

frogg start --web-ui

or set features.webUi.enabled: true in config, or FROGG_WEB_UI_ENABLED=true.

Then open http://<daemon-host>:9999/.

Access

The page itself loads without credentials; everything it does goes through the normal access rules:

• From loopback or a private network with LAN trust on, the app opens directly.
• From a public address, the browser sees a pairing page until the daemon is claimed or you pair.
• With a password set, the app asks for it.

The daemon speaks plain HTTP. For HTTPS, put a reverse proxy in front of it and add its hostname to daemon.hostnames; see security.

Differences from the desktop app

• No Remote SSH connections or SSH deploy.
• No QR scanning; use Paste pairing link.
• The browser connects to other daemons only if they allow the origin (daemon.cors.allowedOrigins).

Serve a different build

features.webUi.distDir (or FROGG_WEB_UI_DIST_DIR) serves another web export, for example one you built with npm run build:ui.