gortium/infra
1
1
Fork 0
Code Issues 13 Pull Requests 24 Actions Packages Projects 1 Releases Wiki Activity

feat: add combined Hermes Workspace image with Swarm worker support #54

Open
Hermes wants to merge 10 commits from feat/hermes-workspace-combined into master
pull from: feat/hermes-workspace-combined
merge into: gortium:master
Conversation 0 Commits 10 Files Changed 4 +6 -1
Hermes commented 2026-05-20 00:50:26 +00:00
Collaborator
Copy Link

Description

Image combinée Hermes Agent + Hermes Workspace pour le support Swarm Mode (workers tmux) dans un Docker.

Architecture

hermes-workspace (IMAGE COMBINÉE)
├── Hermes Agent (notre fork custom: outils, GPU, Piper)
├── Hermes Workspace web UI (Node.js)
├── tmux pour Swarm workers
└── hermes CLI dispo pour spawner des workers

hermes (IMAGE EXISTANTE, inchangée)
└── Gateway + dashboard sur ports 8642/9119

Nouveaux fichiers

assets/compose/ai/hermes-workspace/ :

  • Dockerfile — multi-stage build
    • Stage 1 : clone + build Hermes Workspace from source (pnpm)
    • Stage 2 : part de nousresearch/hermes-agent:latest, applique notre fork Hermes + ajoute Node.js/tmux + copie les artifacts workspace
  • entrypoint-combined.sh — attend que le gateway soit healthy, puis lance le workspace
  • himalaya-ro.sh — copié depuis hermes/ pour l'email

Le dossier assets/compose/ai/hermes/ original est conservé intact — fallback si l'image combinée pose problème.

compose.yml

  • hermes — HERMES_DASHBOARD=1 + healthcheck (inchangé)
  • hermes-workspace — build depuis ./hermes-workspace, SSH build
    • Se connecte à hermes:8642 (gateway) et :9119 (dashboard)
    • Volume partagé Hermes data
    • Traefik sur workspace.lazyworkhorse.net
    • Réseaux : ai_backend + ai_net

Swarm workers

L'image combinée contient tmux + hermes CLI. Les Swarm workers peuvent être spawnés depuis le conteneur workspace via le Conductor, avec leur propre profil et mémoire persistante. Ils communiquent avec le gateway principal via HTTP.

Prérequis .env (agenix)

HERMES_WORKSPACE_PASSWORD=<mot-de-passe>

Notes

  • L'image se reconstruit à chaque docker compose build (mais seulement quand la branche workspace change)
  • La première build prend ~15min (clone workspace + pnpm install + build)
  • La première fois que le workspace se lance, il faut compléter l'onboarding (connection au gateway)
  • Les workers Swarm utilisent ~/.hermes/profiles/<workerId>/ sur le volume partagé
## Description Image combinée Hermes Agent + Hermes Workspace pour le support Swarm Mode (workers tmux) dans un Docker. ## Architecture ``` hermes-workspace (IMAGE COMBINÉE) ├── Hermes Agent (notre fork custom: outils, GPU, Piper) ├── Hermes Workspace web UI (Node.js) ├── tmux pour Swarm workers └── hermes CLI dispo pour spawner des workers hermes (IMAGE EXISTANTE, inchangée) └── Gateway + dashboard sur ports 8642/9119 ``` ## Nouveaux fichiers `assets/compose/ai/hermes-workspace/` : - **`Dockerfile`** — multi-stage build - Stage 1 : clone + build Hermes Workspace from source (pnpm) - Stage 2 : part de `nousresearch/hermes-agent:latest`, applique notre fork Hermes + ajoute Node.js/tmux + copie les artifacts workspace - **`entrypoint-combined.sh`** — attend que le gateway soit healthy, puis lance le workspace - **`himalaya-ro.sh`** — copié depuis `hermes/` pour l'email Le dossier `assets/compose/ai/hermes/` original est conservé intact — fallback si l'image combinée pose problème. ## compose.yml - **`hermes`** — `HERMES_DASHBOARD=1` + healthcheck (inchangé) - **`hermes-workspace`** — build depuis `./hermes-workspace`, SSH build - Se connecte à `hermes:8642` (gateway) et `:9119` (dashboard) - Volume partagé Hermes data - Traefik sur `workspace.lazyworkhorse.net` - Réseaux : `ai_backend` + `ai_net` ## Swarm workers L'image combinée contient `tmux` + `hermes` CLI. Les Swarm workers peuvent être spawnés depuis le conteneur workspace via le Conductor, avec leur propre profil et mémoire persistante. Ils communiquent avec le gateway principal via HTTP. ## Prérequis .env (agenix) ```env HERMES_WORKSPACE_PASSWORD=<mot-de-passe> ``` ## Notes - L'image se reconstruit à chaque `docker compose build` (mais seulement quand la branche workspace change) - La première build prend ~15min (clone workspace + pnpm install + build) - La première fois que le workspace se lance, il faut compléter l'onboarding (connection au gateway) - Les workers Swarm utilisent `~/.hermes/profiles/<workerId>/` sur le volume partagé
Hermes added 1 commit 2026-05-20 00:50:27 +00:00
feat: add combined Hermes Workspace image with Swarm support d064bfb770 
- Update compose submodule to feat/hermes-workspace-combined
- New ai/hermes-workspace/ Dockerfile combining our Hermes fork
  + workspace web UI + tmux (Swarm workers)
- Hermes dashboard enabled on port 9119
- Existing hermes/ Dockerfile preserved as fallback
Hermes added 1 commit 2026-05-20 01:23:29 +00:00
feat(hermes): update compose submodule — drop fork overlay for v0.12.0 kanban b85513ade2
Hermes added 1 commit 2026-05-20 01:29:58 +00:00
Revert "feat(hermes): update compose submodule — drop fork overlay for v0.12.0 kanban" c7a0a4dae4 
This reverts commit b85513ade2.
Hermes added 1 commit 2026-05-20 18:04:33 +00:00
fix(compose): update compose submodule to feat/hermes-workspace-combined (dashboard + auth) 1898f39d24
Hermes added 1 commit 2026-05-20 18:05:48 +00:00
Revert "fix(compose): update compose submodule to feat/hermes-workspace-combined (dashboard + auth)" 8e896e4c0d 
This reverts commit 1898f39d24.
Hermes added 1 commit 2026-05-20 18:06:04 +00:00
fix: update compose submodule — hermes-workspace HOST fix and entrypoint improvements 146c164c91
Hermes added 1 commit 2026-05-20 18:06:36 +00:00
fix(compose): update submodule to fix/hermes-build (dashboard + auth) 68b7c40a9e
Hermes added 1 commit 2026-05-20 18:07:03 +00:00
feat(secrets): add HERMES_WORKSPACE_PASSWORD to containers.env a322ed0884
Hermes added 1 commit 2026-05-20 18:08:11 +00:00
fix: update compose submodule — hermes-workspace HOST fix 8025607a53
Hermes added 1 commit 2026-05-20 18:10:13 +00:00
Revert "fix: update compose submodule — hermes-workspace HOST fix" ff129019e0 
This reverts commit 8025607a53.
This pull request has changes conflicting with the target branch.
  • assets/compose
  • secrets/containers.env.age
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin feat/hermes-workspace-combined:feat/hermes-workspace-combined
git checkout feat/hermes-workspace-combined
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Hermes gortium
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: gortium/infra#54
No description provided.
Delete Branch "feat/hermes-workspace-combined"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?