hermes - 💡(How to fix) Fix Feature request: Auto-start dashboard with gateway systemd service [1 comments, 2 participants]

TL;DR

Create a separate systemd service for the Hermes dashboard to ensure it auto-starts after the gateway and survives WSL restarts or gateway crashes.

Guidance

• Define a systemd service file for the Hermes dashboard with the proposed configuration to establish a dependency on the gateway service.
• Ensure the ExecStart command includes the correct path to the Python executable and the Hermes dashboard script.
• Set the Restart option to on-failure to automatically restart the dashboard service if it crashes.
• Reload the systemd daemon and enable the new service to start automatically after a reboot.

Example

The provided systemd service configuration can be used as a starting point:

[Unit]
Description=Hermes Agent Dashboard
After=hermes-gateway.service
Wants=hermes-gateway.service

[Service]
Type=simple
User=<hermes_user>
Group=<hermes_user>
ExecStart=<venv_path>/python3 <hermes_path>/hermes dashboard --host 0.0.0.0 --no-open --insecure
WorkingDirectory=<hermes_agent_dir>
Restart=on-failure
RestartSec=10

[Install]
WantedBy=multi-user.target

Replace <hermes_user>, <venv_path>, <hermes_path>, and <hermes_agent_dir> with the actual values for your environment.

Notes

The --insecure flag is used when binding to 0.0.0.0, which may not be suitable for all environments. Consider binding to localhost if possible.

Recommendation

Apply the proposed workaround by creating a separate systemd service for the Hermes dashboard, as it provides a reliable solution for ensuring the dashboard survives WSL restarts and gateway crashes.