The previous approach used a /usr/bin/hermes shim to proxy commands from root to the hermes user, and a hand-crafted system-level systemd unit for the gateway. This worked for the default profile but broke down for named profiles: - hermes profile create <name> generates an alias script in ~/.local/bin/<name> that calls hermes with -p <name>. These aliases live in the hermes user's PATH, not root's, so root could not invoke them. - Maintaining parity would require per-profile shims, a watcher daemon to create/remove them, and system-unit mirrors for each profile gateway — all of which would need to stay in sync with hermes internals across updates. New approach — work with hermes, not around it: - loginctl enable-linger hermes: ensures the hermes user's systemd session starts at boot and persists without login. All user-unit gateways (default and per-profile) now survive reboots automatically. - Gateway service management delegated entirely to hermes: 'hermes gateway install' / 'hermes setup' create and enable the user unit natively. The install script no longer pre-installs the gateway; hermes prompts the user to do so at the end of 'hermes setup'. - hermes-dashboard.service remains a system unit (no native install command exists for it). Its After= no longer references hermes-gateway.service since there is no system-unit gateway to depend on. - /usr/bin/hermes shim removed. Root is guided to 'su - hermes' via a two- line /etc/profile.d/hermes-hint.sh message on login, with a one-liner to make the switch automatic. Once logged in as hermes, all hermes commands, profile aliases, and gateway management work natively. - update_script simplified: only hermes-dashboard (our unit) is stopped and restarted. hermes update --yes handles gateway service lifecycle itself.
68 lines
2.0 KiB
Bash
68 lines
2.0 KiB
Bash
#!/usr/bin/env bash
|
|
source <(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVED/main/misc/build.func)
|
|
# Copyright (c) 2021-2026 community-scripts ORG
|
|
# Author: Stephen Chin (steveonjava)
|
|
# License: MIT | https://github.com/community-scripts/ProxmoxVED/raw/main/LICENSE
|
|
# Source: https://hermes-agent.nousresearch.com/
|
|
|
|
APP="Hermes Agent"
|
|
var_tags="${var_tags:-ai;automation;agent}"
|
|
var_cpu="${var_cpu:-2}"
|
|
var_ram="${var_ram:-4096}"
|
|
var_disk="${var_disk:-20}"
|
|
var_os="${var_os:-debian}"
|
|
var_version="${var_version:-13}"
|
|
var_unprivileged="${var_unprivileged:-1}"
|
|
|
|
header_info "$APP"
|
|
variables
|
|
color
|
|
catch_errors
|
|
|
|
function update_script() {
|
|
header_info
|
|
check_container_storage
|
|
check_container_resources
|
|
|
|
if [[ ! -x /home/hermes/.local/bin/hermes ]]; then
|
|
msg_error "No ${APP} Installation Found!"
|
|
exit
|
|
fi
|
|
|
|
msg_info "Stopping Services"
|
|
systemctl stop hermes-dashboard
|
|
msg_ok "Stopped Services"
|
|
|
|
msg_info "Updating ${APP}"
|
|
$STD env \
|
|
HOME=/home/hermes \
|
|
HERMES_HOME=/home/hermes/.hermes \
|
|
/home/hermes/.local/bin/hermes update --yes
|
|
chown -R hermes:hermes /home/hermes
|
|
msg_ok "Updated ${APP}"
|
|
|
|
msg_info "Starting Services"
|
|
systemctl start hermes-dashboard
|
|
msg_ok "Started Services"
|
|
msg_ok "Updated successfully!"
|
|
exit
|
|
}
|
|
|
|
start
|
|
build_container
|
|
description
|
|
|
|
msg_ok "Completed successfully!\n"
|
|
echo -e "${CREATING}${GN}${APP} setup has been successfully initialized!${CL}"
|
|
echo -e "${INFO}${YW} Connect via SSH and configure your LLM provider:${CL}"
|
|
echo -e "${TAB}${GATEWAY}${BGN}ssh root@${IP}${CL}"
|
|
echo -e "${TAB}${BGN}su - hermes${CL}"
|
|
echo -e "${TAB}${BGN}hermes setup${CL}"
|
|
echo -e "${INFO}${YW} API Server (OpenAI-compatible):${CL}"
|
|
echo -e "${TAB}${GATEWAY}${BGN}http://${IP}:8642/v1${CL}"
|
|
echo -e "${INFO}${YW} API key stored at:${CL}"
|
|
echo -e "${TAB}${BGN}/home/hermes/.hermes/.env${CL}"
|
|
echo -e "${INFO}${YW} Web Dashboard (via SSH tunnel):${CL}"
|
|
echo -e "${TAB}${BGN}ssh -fNL 9119:localhost:9119 root@${IP}${CL}"
|
|
echo -e "${TAB}${BGN}Then open: http://localhost:9119${CL}"
|