Skip to content

How it fits together ​

   me (browser)      GitHub push       Telegram
        \                 |                /
         \                |               /
          +----------- Cloudflare -------+      DNS, TLS, login wall, R2 backups
                          |
                 only path into the box
                          |
   +------------------- the server ---------------------+
   |  Coolify   my apps   n8n   ops page   event bus     |
   |  claude-runner   Postgres per app                   |
   +----------------------------------------------------+

The server ​

A netcup VPS 1000 ARM in Vienna: 4 ARM cores, 8 GB RAM (plus 4 GB swap), 128 GB disk, Ubuntu 24.04.

Because it's ARM, every image has to have an arm64 build. Most do. When one doesn't, the build fails.

What runs on it ​

ThingAddressWhat I use it for
Coolifycoolify.stu-bot.ukDeploys, env vars, databases, backups, logs
Ops pageops.stu-bot.ukOne page showing whether everything is OK
n8nn8n.stu-bot.ukAutomations and incoming webhooks
Event businternal onlyServices sending each other messages
Claude runnerinternal onlyClaude Code jobs on the server, and the Telegram chat
These docsdocs.stu-bot.ukYou're reading them

Apps each get their own <name>.stu-bot.uk.

The one rule ​

The server only accepts web traffic that comes through Cloudflare. Anything that tries to talk to it directly is dropped. That's what makes the Cloudflare login wall mean something, because there's no way round it.

SSH is the exception. It's open, but only with my key.