Verify your server’s hostname, run the installer, and get the site ready for your club.
You’ll install Field Day Commander on one Linux computer, then open it from a laptop on the same network. This guide covers a fresh install on Raspberry Pi OS, Debian, or Ubuntu. For Docker and advanced options, use the installation reference.
sudo. SSH & Command-Line Basics covers connecting.If you’re connected over SSH, your terminal is already running commands on the server. Keep that session open. The headers on each command block tell you which computer to use. “On your laptop” means a local terminal outside the SSH session; “On the server” includes commands you run through SSH.
The hostname gives your operators an address to open in their browsers. On the server, run:
hostname
The Pi setup guide uses fd-commander as its example name. With mDNS working, that becomes fd-commander.local on your network. If you chose a different device name, substitute it in the examples below. Installing Field Day Commander won’t change the name.
On your laptop, open a separate terminal outside the SSH session and check that the name resolves:
ping fd-commander.local
You should see the server’s IP address. Press Ctrl+C to stop ping. To confirm it’s the right machine, compare that address with the output of hostname -I on the server. If the name isn’t found or the address doesn’t match, sort out hostname resolution before continuing.
A hostname provided by your router’s local DNS works too. The important part is that your laptop can resolve it to the server. See Raspberry Pi’s hostname and address-discovery instructions for more detail.
Back in the server terminal, install Git if needed, download Field Day Commander, and enter its directory. These commands are for Raspberry Pi OS, Debian, and Ubuntu:
sudo apt update sudo apt install git git clone https://github.com/ckoval7/fielddaycommander.git cd fielddaycommander
Then run the installer. Replace YOUR_SERVER_HOSTNAME with the name you verified in step 1, such as fd-commander.local. Include the .local suffix if you used it for the check, but leave out http:// and any trailing slash:
sudo ./deploy.sh --domain YOUR_SERVER_HOSTNAME
The --domain option tells the web server which address to serve. It doesn’t create that hostname. Keep the verified name handy; you’ll use the same one in your browser.
The installer handles the dependencies, database, web server, and background services. Let it finish and keep the terminal open. A Pi can take longer than a desktop. If your SSH connection is unreliable, tmux lets the installation continue through a disconnection.
This installs the site for local-network access over HTTP. For public access with HTTPS, follow DNS & TLS Setup. Custom ports and other options are in the deployment flags reference.
On your laptop · Web browser
On your laptop, open http:// followed by the hostname you used in the install command. If you deployed with fd-commander.local, open http://fd-commander.local.
You should see the initial setup wizard. Set the administrator password, choose your site branding, and enter your organization details and preferences. Store the password somewhere safe, then sign in with admin@localhost and that password. First Event Setup explains the wizard fields if you need help.
On another laptop, tablet, or phone · Web browser
Open the same address on another laptop, tablet, or phone connected to your LAN. If the site loads, the server is ready for event setup. Write down the working browser address for your operators.
Repeat this check with the devices and network you’ll use at Field Day. A hostname that works at home may need network configuration at the site; Set Up a LAN for Field Operations walks through that.
You don’t need to log a contact to check the installation. Logging needs an event whose operating window is open. Use the multi-station practice procedure when you’re ready to test logging.
Check the output of hostname on the server and make sure you’re using that exact name. Both devices must be on the same network; guest Wi-Fi may isolate them. A ping timeout can mean replies are blocked, while “could not find host” or “name not known” means the name didn’t resolve.
If mDNS isn’t available, use a local DNS name configured through your router or ask your club’s network administrator. As a fallback, use the server’s actual LAN IP for both --domain and browser access. Give it a DHCP reservation or fixed IP.
Check that installation finished successfully and that you’re using http:// with the exact hostname supplied to --domain. Another hostname or IP pointing at the same computer may not serve the site. If you change the chosen address, re-run deployment with the new --domain value.
On the server, check the web service and recent logs:
sudo systemctl status fdcommander --no-pager sudo journalctl -u fdcommander --since "10 minutes ago" --no-pager
If the service is running, check the firewall and Wi-Fi client isolation. SSH Basics covers the other services and application logs.
If Git reports that fielddaycommander already exists, check the directory before continuing. An existing installation needs the update procedure.
For an installer error, read the failed step and check /var/log/fd-commander-deploy.log. Confirm internet access, free disk space, and a supported OS before retrying. When asking for help, share the relevant error text with passwords and other private values removed.
Prepare your field network, then follow First Event Setup to create the event, configure stations, and invite operators. Set up backups before relying on the server for your event.
Once installed, core logging and event operation work on your local network without internet. Internet-fed weather information and optional email still need their respective connectivity and services.