solar wagon
If Hermes Agent is running in Docker, a new profile can be created on the mounted volume — but can this new profile actually be used? A second gateway cannot be started within the same container.
What is the difference between the profile-based approach and running separate Hermes server instances, each with its own dedicated gateway?
hasty pond
@chrome sphinx
chrome sphinx
If Hermes Agent is running in Docker, a new profile can be created on the mounte...
Honestly, just use multiple containers with a different .hermes directory mounted. You get the exact same effect in a much more docker native way. The multi profile feature does exactly the same thing under the hood.
outer oak
Honestly, just use multiple containers with a different .hermes directory mounte...
What's the benefit? Is your suggestion easier to maintain? Since Docker has established UI?
new to the multi profile architecture since my single agent is doing too much.
context pollution getting bad.
chrome sphinx
They are two different ways to achieve the exact same end result. There is no difference to the outcome, they both end up with a .hermes directory per profile.
The built in method doesn't work very well for containers as it wants to create multiple gateways, etc per profile - each of which you would need to reconfigure the container for.
Doing it the container way means you won't have port clashes, etc. It gives you a lot more control.