Open setup questions for running Hermes on a VPS

Hermes can be installed inside a container on a VPS so it keeps working even when the personal computer is not in use. The main setup problem is how to organize and view files. are being kept in Obsidian and synced to a laptop every day, but it is unclear how best to inspect and manage Hermes’s own file structure.

There is also about whether files like agents.md should live in Obsidian or stay in the native on the server. Another problem is : the web does not give a good enough view of what Hermes is currently doing. Using the to control a Hermes instance on a VPS may be possible, but the setup appears messy.

The broader work-structure question is how to arrange everyday life work, large projects, subprojects, and tasks across folders, profiles, and kanbans. It is also unclear whether projects should share profiles, share kanbans, or start the main chat inside or outside a project folder.

Key points

  • Running Hermes in a container on a VPS can keep it active while the main computer is away or off.
  • Obsidian may work well for , but Hermes’s own files may need a separate structure.
  • Files such as agents.md need a clear home: either in the note system or in the native .
  • The web may not be enough for quickly understanding what Hermes is doing.
  • Project folders, profiles, kanbans, and chat start locations need a planned structure before heavy use.

Sources covering this story (5)

Read original