GESD32 Technology Department • Operational Checklist

Hermes / Vegeta installation guide with progress tracking.

A modern, step-by-step implementation view for deploying Hermes Agent as Vegeta, connecting Telegram, securing the instance, and publishing the documentation site through GitHub and Hostinger.

Open full guide

Deployment Progress

0 of 0 complete

0Core complete

0Security complete

0Publishing complete

Security Boundary

Internal documentation is excluded from publishing.

The Hostinger build publishes `index.html`, `docs/`, `public/`, and `assets/`. It intentionally excludes `internal/` unless access controls are verified.

Operational Scope

Define what the instance is responsible for before configuring systems.

IDENTITY

Mission baseline

Confirm the instance identity is Vegeta.Operational intelligence partner for the Technology Director and the GESD32 Technology Department. Confirm primary use cases.Operational support, documentation, monitoring, escalation, project visibility, automation, and future integrations. Confirm sensitive data rules.No API keys, tokens, passwords, or staff-sensitive content in public documentation paths.

Server Preparation

Prepare a stable Ubuntu server with the right baseline packages and security posture.

FOUNDATION

Server baseline

Select Ubuntu Server LTS.22.04 LTS or 24.04 LTS recommended. Confirm capacity.Minimum: 2 vCPU, 4 GB RAM, 40 GB storage. Preferred: 4 vCPU, 8–16 GB RAM, 100 GB SSD. Use a clear hostname.Recommended: vegeta, hermes-vegeta, or gesd32-vegeta.

Server commands

Update the server.sudo apt update && sudo apt upgrade -y Install base packages.sudo apt install -y curl git python3 python3-pip python3-venv build-essential ca-certificates tmux jq unzip Enable systemd linger for gateway persistence.sudo loginctl enable-linger $USER Apply firewall baseline if appropriate.sudo apt install -y ufw && sudo ufw allow OpenSSH && sudo ufw enable

Hermes Installation and Configuration

Install Hermes, configure model/provider, tools, and production safety settings.

HERMES

Install and health check

Install Hermes Agent.curl -fsSL https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.sh | bash Reload shell and verify command.

source ~/.bashrc
which hermes
hermes --version

Run Hermes health check.hermes doctor

Configuration

Run setup wizard.hermes setup Select model/provider.hermes model Store secrets only in `.env`.Use `hermes config env-path`; do not place secrets in Markdown or public docs. Enable secret redaction if needed.hermes config set security.redact_secrets true

Recommended Vegeta toolsets

Enable operational toolsets intentionally.terminal, file, web, browser, skills, memory, session_search, cronjob, delegation, messaging, todo, vision, and optional tts.hermes tools

Telegram Gateway Setup

Connect Vegeta to Telegram and install the gateway as a persistent background service.

Bot and gateway

Create the Telegram bot through @BotFather.Do not paste the bot token into chats, screenshots, or documentation. Configure Hermes Gateway.hermes gateway setup Test gateway in foreground.hermes gateway run Install and start gateway service.

hermes gateway install
hermes gateway start
hermes gateway status

Telegram operations

Set the home channel./sethome Verify gateway session from Telegram.

/status
/platforms

Separate DM and group use cases.Technology Director DM for sensitive/executive work. GESD32 Tech Operations group for approved operational questions and ClickUp visibility.

Verification Checklist

Validate CLI, model, tools, gateway, identity, and operational response style.

VERIFY

Acceptance checks

CLI verification passes.

hermes --version
hermes doctor
hermes status --all

Model test succeeds.hermes chat -q "Respond with: Hermes model test successful." Gateway verification succeeds.hermes gateway status Vegeta identity confirmed in Telegram.Expected: responds as Vegeta, identifies the Technology Director as primary operator/director, uses operational language, and avoids generic chatbot behavior.

Vegeta Operational Prompt

Apply the production identity, operating mindset, severity model, and verification rules.

PERSONA

Prompt application

Apply the Vegeta production prompt.Preferred placement: system/personality configuration, pinned profile/personality prompt, skill/directive file, or initialization prompt. Confirm the operational priorities are active.Classroom uptime, student learning continuity, infrastructure reliability, cybersecurity, accountability, visibility, documentation, automation, strategic planning. Confirm verification integrity rules.Distinguish verified facts, observations, inferences, speculation, and recommendations. Do not fabricate metrics or operational outcomes.

Backup and Recovery

Protect the Hermes home directory, credentials, memories, sessions, and operational knowledge.

RESILIENCE

Backup scope

Identify important paths.config.yaml, .env, auth.json, state.db, skills, sessions, logs, operations, cron. Create a secure backup plan.

mkdir -p ~/backups
tar -czf ~/backups/hermes-backup-$(date +%F).tar.gz ~/.hermes

Backup warning

Backups may include secrets from `.env` and `auth.json`. Store securely. Do not upload backups to public or unmanaged storage.