Skip to content

Operate

Running a Jarvis Automation server day to day: the jarvisd command, where the data lives and how to back it up, the ports nodes and phones use, what reaches the internet, and what to do when something doesn't connect.

Jarvis Automation is a pre-release (release candidate rc18). Builds are on the releases page; each one is marked Pre-release. These pages describe rc18 and say where the next release differs.

Page Read it to
The jarvisd command Look up a command: the service, doctor, setup-link, upgrade, the imports.
Data and backups Find the data directory on your system, back it up and restore it.
Ports, firewall and mDNS See which ports to open, let your network through the firewall, and how phones find the server.
Network egress and offline mode See everything that can reach the internet, and keep the server offline.
Troubleshooting Fix a server that doesn't start or that phones and nodes can't reach.
Security Read how Jarvis handles accounts, keys and your data.

The commands you'll use most

jarvisd service status     # is it running, and does it answer?
jarvisd doctor             # can nodes and phones reach it?
sudo jarvisd doctor --fix  # open the firewall to your local network
sudo jarvisd setup-link    # the setup wizard's link again
jarvisd service restart    # after editing jarvisd.env

On Windows, run them in an Administrator PowerShell instead of with sudo.

Running the old Docker install? Its pages are frozen under Legacy, including its environment variables, configuration and troubleshooting.