Worker Installation

macOS worker installation

This guide connects a macOS host to an existing LyftData server as a worker. All commands require administrator privileges.

Before you begin

Complete the installation prerequisites, ensure the worker binary is available at /usr/local/bin/lyftdata-worker, and generate a worker ID plus API key on the server. Verify access with lyftdata-worker --version.

Prepare the worker account

Note

Follow the macOS service account template with user lyftdata-worker and data directory /var/lib/lyftdata-worker.

Success criteria

• sudo launchctl list | grep com.lyftdata.worker shows the service with exit code 0.
• The worker card in the UI shows Online and polls within the default 15-second interval.
• sudo tail -n 50 /var/lib/lyftdata-worker/worker.log contains Connected to server without error lines.

Install the launch daemon

Create /Library/LaunchDaemons/com.lyftdata.worker.plist:

sudo tee /Library/LaunchDaemons/com.lyftdata.worker.plist >/dev/null <<'EOF'
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>Label</key>
  <string>com.lyftdata.worker</string>
    <key>ProgramArguments</key>
    <array>
      <string>/usr/local/bin/lyftdata-worker</string>
    </array>
  <key>EnvironmentVariables</key>
  <dict>
    <key>LYFTDATA_WORKER_ID</key>
    <string>worker-01</string>
    <key>LYFTDATA_WORKER_API_KEY</key>
    <string>&lt;your-api-key&gt;</string>
    <key>LYFTDATA_URL</key>
    <string>https://server-host:3000</string>
    <key>LYFTDATA_TLS_INSECURE</key>
    <string>true</string>
    <key>LYFTDATA_JOBS_DIR</key>
    <string>/var/lib/lyftdata-worker</string>
    <key>LYFTDATA_LICENSE_EULA_ACCEPT</key>
    <string>yes</string>
  </dict>
  <key>RunAtLoad</key>
  <true/>
  <key>KeepAlive</key>
  <true/>
  <key>StandardOutPath</key>
  <string>/var/lib/lyftdata-worker/worker.log</string>
  <key>StandardErrorPath</key>
  <string>/var/lib/lyftdata-worker/worker-error.log</string>
  <key>UserName</key>
  <string>lyftdata-worker</string>
  <key>WorkingDirectory</key>
  <string>/var/lib/lyftdata-worker</string>
</dict>
</plist>
EOF
sudo chmod 644 /Library/LaunchDaemons/com.lyftdata.worker.plist

Load the worker:

sudo launchctl load -w /Library/LaunchDaemons/com.lyftdata.worker.plist

Optional settings

Add or adjust plist environment variables to tune behaviour—for example, update `LYFTDATA_URL` when migrating environments. Each `key`/`string` pair in the `<dict>` maps directly to a `lyftdata-worker` flag.

If the server is using the default self-signed certificate, keep LYFTDATA_TLS_INSECURE=true for evaluation and remove it once you install a trusted certificate.

Verify the worker

# Check launchctl status
sudo launchctl list | grep com.lyftdata.worker

# Tail the worker log
sudo tail -n 50 /var/lib/lyftdata-worker/worker.log

Confirm in the server UI that the worker appears online. If it does not, double-check the worker ID, API key, and server URL in the plist and re-run launchctl load -w.

Next steps

• Deploy jobs to the worker from the server UI
• Repeat on additional hosts to scale out
• Follow the post-install checklist for metrics and job editor tips