Docker and Kubernetes
Run Hervi’s assistant in a container, and add the Hervi plugin with docker exec, a copy, or an init container.
Hermes runs well in a container, on a home server, a NAS or a cluster. The steps are the same as in Getting started; only how you run the commands changes.
Docker
Run the plugin commands inside the container, with the image’s own hermes and its home (/opt/data in Hermes’s
image):
docker exec -it <container> hermes -p family-anna plugins install https://github.com/dillonbrowne/hervi-plugin --no-enable
docker exec -it <container> hermes -p family-anna plugins enable hervi
docker restart <container>
Or copy the plugin folder into the data volume, making the profile’s plugins folder first:
docker exec <container> mkdir -p /opt/data/profiles/family-anna/plugins
docker cp plugin <container>:/opt/data/profiles/family-anna/plugins/hervi
Then add enabled: [hervi] under plugins: in that profile’s config.yaml. To update a copy, delete the old
hervi folder first.
Kubernetes
The profiles live on the volume. In a pod with more than one container, name Hermes’s container in every
kubectl exec and kubectl cp (-c <container>).
- Bake it in (best for a locked-down cluster): ship the plugin folder at a pinned commit in your image or a
ConfigMap, and have an init container copy it into
$HERMES_HOME/profiles/<profile>/plugins/hervion every start. Writeplugins.enabled: [hervi]from the init container too, before Hermes starts. A ConfigMap’s keys are flat, so map the plugin’s subfolders (contract/,dashboard/,dashboard/dist/) withitemspaths. - Copy it in:
kubectl cp plugin <namespace>/<pod>:/opt/data/profiles/family-anna/plugins/hervi, then edit the profile’sconfig.yamland restart the pod. - Install in the pod:
kubectl exec -it <pod> -- hermes -p family-anna plugins install https://github.com/dillonbrowne/hervi-plugin --no-enable, thenplugins enable hervi. The pod needsgitand a route to the repository.
Reaching it
One way for the phones to reach the dashboard is Tailscale: run it on the host, or as a sidecar, and serve the
dashboard’s port over HTTPS inside your tailnet. A reverse proxy or a gate such as Cloudflare Access works too. Either
way, set HERMES_DASHBOARD_PUBLIC_URL to exactly the address the phones use, path included if Hermes is served under one.