stage-uxl and keeping it there.The box is the source of truth, not this wiki. Versions, ports, role names and
directory modes drift as people edit the box. Every page names the command that
produced its facts — where the two disagree, believe the box, then fix the page in
the same sitting.
¶ Start here
- Platform The box itself — OS, Docker, Caddy, PostgreSQL, RabbitMQ, Redis, accounts, groups, networks, port allocation
- Pipeline How a push becomes a running container — the GitHub Action, the self-hosted runner, branch mapping, image naming, the deploy script
- Onboarding Putting a new service on the box — Dockerfile, environment, provisioning, DNS, Caddy, the first deploy
- Operations Day 2 — logs, restart, redeploy, rollback, configuration changes, migrations, pruning disk
- Reference Troubleshooting by symptom, the FAQ, and the list of known open items
- Services One page per package on the box, with its index, hostname, environment and quirks
¶ The shape of it, in one picture
git push to `staging`
│
▼
GitHub Actions ──▶ self-hosted runner `stage-uxl-1` (runs ON the box, as ghrunner)
│ │
│ ├── grep NEXT_PUBLIC_ out of the environment's .env ──▶ build.env
│ ├── docker build (Dockerfile: COPY build.env .env.production)
│ ├── docker push ghcr.io/leveraged-growth/<pkg>:<git-sha>
│ └── /opt/uxl.club/bin/deploy staging <pkg> <sha>
│ │
▼ ▼
docker compose up -d
env_file: the SAME .env (server-side values)
container staging-<pkg>
published on 127.0.0.1:56NN
│
▼
Caddy ──▶ https://stage-<name>.uxl.codes
Four facts follow from that picture and explain most of everything else:
- The builder and the deploy target are the same machine. No SSH hop, no deploy
key, no registry round-trip for a fresh build. - One file per environment holds all of its configuration. The pipeline splits
it —NEXT_PUBLIC_*compiles into the bundle, the rest is handed to the container
at run time and never enters the image. - The branch decides the environment, and nothing else can. A manual dispatch
cannot redirect a build. - Nothing is public except Caddy. Every container publishes on
127.0.0.1only.
¶ The box at a glance
| Host | stage-uxl · 72.61.173.12 · Hostinger VPS · Ubuntu 24.04 |
| Environments | staging for everything; development for GrowthCommand only, for historical reasons |
| Ports | development = 5500 + index, staging = 5600 + index — the allocation table is the authority |
| Data services | PostgreSQL 18, RabbitMQ 4.3.4, Redis — all native on the host, not containerised |
| Ingress | Caddy, one site file per hostname, automatic Let's Encrypt |
| Timezone | IST, deliberately, in three independent places |
¶ Editing this wiki
This wiki and Leveraged-Growth/wiki-backup
are the same content in two places, reconciled every five minutes in both directions.
Edit whichever suits the change:
- In the browser — good for a paragraph, a correction, a new page.
- In git — good for bulk edits, review, or anything you want a second pair of eyes
on. Pages are markdown with YAML front matter and the file path mirrors the page
path.
Keep the front matter when editing in git; it carries the title, publish state and
tags.
Deleting a file in the repository deletes the live page on the next sync. It is a
two-way mirror, not a backup.
¶ What is deliberately not here
Production. It runs on a Coolify host built from the repository directly, not on
this box. Since 14 August 2026 a push to main builds nothing at all. There is no
/opt/uxl.club/production and it must not be created.
Local development. Developers run that on their own machines. GitHub Actions
never builds a development branch — a decision, not an omission.
Passwords. No credential appears anywhere in this wiki. Where one is needed, the
page names the file on the box or the 1Password item that holds it.