Remote Deployment Inventory
This directory stores AGENT-style operational documents for remote hosts and deployed projects.
Purpose
Use this directory to keep host-level deployment facts in one place so they do not get lost across shell history, chat logs, or ad hoc notes.
Keep these documents focused on runtime reality:
- where a service actually runs
- which port is really exposed
- where the real data lives
- which repo is writable versus mirrored
- how to inspect, restart, back up, and upgrade
File Layout
TEMPLATE.AGENT.md— reusable template for a new remote host or VM<host>.AGENT.md— filled document for a specific host
Naming Convention
Use the stable host name in the file name when possible.
Examples:
minione-ubuntu-infra-4c16g120g.AGENT.mdprod-k8s-edge-01.AGENT.mdstaging-gpu-node-02.AGENT.md
Suggested Update Rules
Update the host document whenever one of these changes:
- deployment mode changes, for example Docker to systemd
- runtime ports or hostnames change
- a new database, cache, or volume is introduced
- Git remotes or mirror strategy changes
- backup location or restore procedure changes
- a real incident reveals a hidden dependency or operational trap
Current Hosts
minione-ubuntu-infra-4c16g120g.AGENT.md