Ryan Hughes
5961a3ff5d
A droplet DigitalOcean still reports as "new" never registers a runner, but the controller counted it as one booting and created no replacement until MAX_AGE_MINUTES. A publish job sat queued for minutes behind one in mkc1. Delete droplets still provisioning after MAX_BOOT_MINUTES (10) and leave them out of the live count, so the same tick creates a replacement.
20 lines
787 B
Bash
20 lines
787 B
Bash
# /etc/omarchy-controller.env — mode 0600, owned by root, read by systemd.
|
|
DIGITALOCEAN_TOKEN=dop_v1_...
|
|
# Fine-grained PAT scoped to the repo: Actions: read, Administration: read+write
|
|
GITHUB_TOKEN=github_pat_...
|
|
REPO=omacom/omarchy-pkgs
|
|
LABEL=omarchy-builder
|
|
TAG=omarchy-builder
|
|
# Builder sizes, tried in order in any region that has them in stock.
|
|
SIZES="g5-32vcpu-64gb-50gb g5-32vcpu-128gb-50gb"
|
|
# Optional: regions to try first, e.g. "ric1". Empty means any.
|
|
REGIONS=
|
|
MAX_DROPLETS=6
|
|
MAX_AGE_MINUTES=200
|
|
# Delete a droplet DigitalOcean still reports as provisioning after this long.
|
|
MAX_BOOT_MINUTES=10
|
|
LOCK=/run/omarchy-controller/lock
|
|
# Operator public keys for root on every builder droplet (JSON array).
|
|
# create.sh fills this from the operators' GitHub keys.
|
|
SSH_KEYS_JSON=[]
|