CLI

Manage your OneSVD node with the onesvd command.

The installer drops an onesvd command onto your PATH. It's how you control the node after install — install.sh itself is just the one-time bootstrap that builds everything and hands off to onesvd up.

Commands#

Command	What it does
`onesvd up`	Build if needed, then install and start the services. The installer runs this for you.
`onesvd start` / `stop` / `restart`	Control the running services.
`onesvd status`	Show service status and the watched directory.
`onesvd logs`	Follow the logs for all three services.
`onesvd build`	Rebuild the watcher, hub, and web client.
`onesvd dir [PATH]`	Show the watched directory, or set it.
`onesvd config`	Print the current configuration.
`onesvd config get <key>`	Print one config value.
`onesvd config set <key> <value>`	Change a config value.
`onesvd uninstall`	Stop and remove the services. Config and data are kept.
`onesvd version`	Print the version.
`onesvd help`	List every command.

Examples#

shell

# point the watcher at a different directory
onesvd dir ~/projects/releases

# change the web UI port
onesvd config set frontend_port 8080

# see what's running and where it's watching
onesvd status

# follow the logs
onesvd logs

Config keys#

onesvd config reads and writes ~/.config/onesvd/config.yml. The keys:

Key	Default	What it does
`watch_dir`	(chosen at install)	The directory the watcher fingerprints.
`hub_port`	`4000`	Hub WebSocket + HTTP port.
`ingest_port`	`4001`	Loopback port the watcher publishes to.
`frontend_port`	`7777`	Web client port.
`frontend_mode`	`prod`	`prod` serves the production build; `dev` runs the dev server.

Changing the watched directory or a port with onesvd dir / onesvd config set rewrites the systemd units and restarts the services automatically when they're running — no separate restart needed.

Where things live#

Path	What
`~/.local/bin/onesvd`	The command (a symlink).
`~/.local/share/onesvd/`	Source checkout and built binaries.
`~/.config/onesvd/config.yml`	Your configuration.