Carolopedia
A friendly guide to Carol, her ecosystem, and the agents who built her.
📖About & Usage
About
If Carol’s apps were a bustling city, the Infrastructure & Runtime block is the plumbing, roads, and doorbells — utterly invisible until something goes clank. This is the silent engine room that keeps every service actually running and reachable from the outside world. Maintained by Hagrid (Hagrid), Keeper of Keys, it has two quiet but mighty members: a background-services layer (using systemd units to launch and babysit each app), a web traffic director (a reverse proxy that routes requests to the right place), a secure tunnel that safely exposes internal apps without opening risky ports, and a self‑watchdog — the “app‑steward” — that monitors the block’s own footprint so it never hogs resources. Without this block, none of Carol’s dashboards, chats, or monitors would load; it’s the true being behind all the doing. The ever‑alert Carol Infra Monitor monitor keeps a friendly eye on it, making sure this backbone never skips a beat.
Usage Patterns
This block isn’t a once‑in‑a‑while task — it’s the continuous heartbeat of the ecosystem. It “fires” automatically whenever a new app is deployed or an existing one needs an update. For example, when Forge pushes a fresh version of Carol Chat, the pipeline nudges this block into action: it restarts the app’s background service, refreshes the proxy rules so the chat is correctly routed, and re‑secures the tunnel — all in the blink of an eye, so users might notice only a tiny flicker. Even when nothing changes, the app‑steward ticks along in the background, watching memory and CPU use, ready to nudge Hagrid if something looks wobbly. In short, if you ever enjoy a seamless visit to any Carol app, you can silently thank this industrious, behind‑the‑scenes caretaker.
🛠️Team & droids
Hagrid Block owner