This article explains how to move Hermes to a new machine while keeping the deployment simple and stable. The two machines are assumed to already be reachable over the network, so the only connectivity checks we need are basic ping, SSH, and container-level verification.
The main goals are:
keep the Hermes data intact, copy the Docker project to the new machine, update the GBrain MCP endpoint, remove any Docker network settings that are no longer needed, verify that Hermes can still reach GBrain after the migration.
This guide shows how to prepare a disk on an NFS server, export it with nfs-kernel-server, troubleshoot common permission problems, and mount the remote NFS share from an OpenMediaVault client using the official Remote Mount plugin.
On the NFS Server Mount the Disk by UUID First, identify the UUID of the disk or partition you want to mount:
sudo blkid Example output:
root@orangepi3:~# sudo blkid /dev/mmcblk2p1: UUID="600d3790-5661-48e4-b40f-16356b83183d" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="b0d8b10d-01" /dev/sdb1: UUID="4fe6face-5253-486d-9c6c-c6658ea036ba" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="ccc2e70a-a1f9-49d6-aecf-36e13ba0a9d4" /dev/mmcblk0p1: UUID="0463846f-1aa0-42b9-bc76-92a8d366d6ed" BLOCK_SIZE="4096" TYPE="ext4" /dev/zram1: LABEL="log2ram" UUID="1514a966-ac2d-4275-9822-f95aee88050f" BLOCK_SIZE="4096" TYPE="ext4" /dev/sda1: UUID="6600936a-8024-462d-a92a-96ce2b73c2c7" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="62fce7c6-3580-a242-bc44-84255f16efb6" /dev/zram0: UUID="11e281ee-50ce-452d-8e35-bef71510b09d" TYPE="swap" Create the mount point if it does not already exist:
1. Installation Open Zoo Code → click ⚙️ → choose Edit Global MCP (for all projects) or Edit Project MCP (saved in .roo/mcp.json).
Paste the following config into the file:
{ "mcpServers": { "gbrain": { "type": "streamable-http", "url": "http://gbrain:7333/mcp", "headers": { "Authorization": "Bearer YOUR_TOKEN" } } } } Note: If the server uses SSE (legacy), change "type" to "sse". Try streamable-http first.
2. Connection check 2a. In the Zoo Code UI Click ⚙️ → view the list of MCP servers Green dot = connection OK Red dot = error → hover to see the message 2b.
Set Up an Agent to Push Directly to a GitHub Repo Goal This guide walks through a gentle, practical way to let an agent such as Hermes commit and push directly to a GitHub repository without placing your main personal GitHub SSH key on the server.
The target architecture is:
Local developer machine -> GitHub repository Hermes agent on server -> commit and push directly to master The server uses a dedicated GitHub machine user and a dedicated SSH key:
This guide shows how to run GBrain as a personal knowledge brain in Docker and connect it to Hermes AI Agent over MCP HTTP. Once connected, Hermes can access more than 70 knowledge, search, graph, and code-intelligence tools exposed by GBrain.
Overview Telegram / Web | v Hermes (Docker) ---- MCP HTTP ----> GBrain (Docker) | v PostgreSQL + pgvector (brain database) Stack Service Image Port hermes nousresearch/hermes-agent:latest 8642 gbrain skywirex/gbrain:latest 7333 gbrain-postgres pgvector/pgvector:pg16 5432 (internal) 1.
This guide shows how to connect OpenCode to a local CLIProxyAPI instance running in Docker and use RTK to compact bash output before OpenCode reads it.
Overview Flow OpenCode -> API call to http://localhost:8317/v1 CLIProxyAPI (Docker) -> forwards through OAuth subscription Claude / Gemini / Codex <- RTK hook compacts bash output before OpenCode reads it Step 1: Check That CLIProxyAPI Docker Is Running docker ps | grep cliproxy # Quick test curl http://localhost:8317/v1/models | jq # If you mapped a different port, replace 8317 accordingly.
This guide provides a comprehensive walkthrough on establishing a secure WireGuard VPN connection between a Virtual Private Server (VPS) and a MikroTik router, enabling seamless access to your home Local Area Network (LAN) from your VPS. It details the necessary configurations for both the VPS and the MikroTik device, covering crucial steps such as WireGuard interface creation, peer setup, IP address assignment, routing, firewall rules, and Network Address Translation (NAT). By following these instructions, you will be able to securely extend your home network’s reach to your VPS, allowing you to interact with LAN devices as if you were directly connected.
This article will guide you through the process of installing Openclaw using Docker and Docker Compose, including preparation, configuration, and service startup steps with Youtube video.
Pros and Cons of Running Openclaw with Docker Pros:
Fast & Isolated Deployment: Quick setup in an isolated environment, reducing host impact. Portable & Resilient: Easy to back up, move, and redeploy with consistent settings; supports 24/7 operation and simplified version management. Secure: Requires fewer direct host permissions.
Part 1: Setting Up NFS on Your OpenMediaVault Server Part 2: Client-Side Automation with Autofs Part 3: Integrating Autofs with Docker (The rshared Magic) Managing network storage can be a headache, especially when you’re dealing with multiple services and containers. Manually mounting NFS shares is tedious, and getting Docker containers to reliably see those shares can be a whole other challenge.
In this post, these issues will be tackled head-on.
