Skip to main content
The floe CLI connects to https://api.floe.one by default. You can point it at any Floe signaling server using the --server flag.

​
Usage

Both sender and receiver must use the same server:
Point --server at the origin that serves /api and /ws. On a one-domain deployment that is the same address your users open in a browser, so this is all you need: the share link that floe send prints resolves to the same origin and opens the web client correctly.

​
When the web client is on a different host

The browser link printed by floe send defaults to the same origin as --server. If your web client lives somewhere else, such as the two-subdomain layout, override it with --web:
Without --web, that split deployment prints a link pointing at the signaling server, which serves no web app.

​
Local testing

To test against a local instance running on the default ports:
The browser link will point to http://localhost:3000 automatically when using localhost:3001. See Self-Hosting for instructions on running your own Floe instance.