Two bugs under one roof.
The visible one: a publisher uploading anything over 10 MB on the live
site got "Network error — Unexpected token '<'" in the browser console.
Cause: the Caddy block I wrote for prometheus.x had
`request_body { max_size 2GB }` nested inside the handle block, where it
is a syntax Caddy parses but does not apply, so Caddy's own 10 MB
default was still the gate. Any oversize POST got Caddy's HTML 413 page,
which the browser's JSON parser choked on at the leading `<`.
Fix: moved `request_body { max_size … }` to the top of the prometheus.x
site block (outside `handle`), where Caddy actually honours it. The live
Caddyfile on p2pexchange is already patched + reloaded; a 50 MB upload
verified through the end-to-end path (Caddy → service → clamd → signed
scan report).
The scope one: 2 GiB was more than Prometheus should offer to publishers
at launch. Mobile apps are usually ~100 MB and even most desktop
installers come in well under 200 MiB. Dropping to 200 MiB:
- Fits every Android APK and most desktop installers.
- Shrinks the operator's Sia storage bill (fewer accidental Steam-size
uploads).
- Keeps the "publishers of larger binaries self-host and submit a
manifest with the external URL + SHA" escape hatch — the scanner
still fetches the URL and checks the hash, so a 5 GB game isn't
locked out, Prometheus just doesn't eat its storage.
Changes:
service/uploads.js MAX_FILE_BYTES default: 2 GiB → 200 MiB
service/pages.js /submit step-1 subtitle: "any size up to
2 GiB" → "up to 200 MiB"
deploy/prometheus-x.conf (unused angie fallback) 2g → 200m
deploy/apps-silentmode-st.conf (unused angie fallback) 2g → 200m
PROMETHEUS_MAX_UPLOAD_BYTES env still overrides per-instance.
|
||
|---|---|---|
| .. | ||
| apps-silentmode-st.conf | ||
| docker-compose.yml | ||
| Dockerfile | ||
| make-tls-cert.sh | ||
| prometheus-service.service | ||
| prometheus-snapshot.service | ||
| prometheus-snapshot.timer | ||
| prometheus-x.conf | ||
| README.md | ||
Prometheus — deploy
Everything in this directory lands on a VPS the first time Prometheus is set up on it, plus files that get swapped out on each release.
deploy/
prometheus-service.service systemd unit — the Node service on :3700
prometheus-x.conf angie vhost — TLS-terminated reverse proxy
prometheus-snapshot.service systemd unit — weekly snapshot job
prometheus-snapshot.timer systemd timer — Sunday 04:00 UTC
apps-silentmode-st.conf angie vhost — SEO mirror (apps.silentmode.st)
make-tls-cert.sh (re-)generate the self-signed cert, print the pin
First-time install (VPS, root)
# Code
useradd -r -s /usr/sbin/nologin -d /opt/prometheus prometheus
mkdir -p /opt/prometheus
rsync -av --exclude=node_modules --exclude=db.sqlite\* --exclude=uploads \
--exclude=.keys --exclude=build \
<workstation>:Prometheus/ /opt/prometheus/
cd /opt/prometheus && npm install --omit=dev
chown -R prometheus:prometheus /opt/prometheus
mkdir -p /opt/prometheus/{uploads,.keys,build}
chown prometheus:prometheus /opt/prometheus/{uploads,.keys,build}
# TLS cert for prometheus.x (prints the fingerprint — save it for #6)
sudo bash /opt/prometheus/deploy/make-tls-cert.sh
# angie
install -m644 /opt/prometheus/deploy/prometheus-x.conf /etc/angie/http.d/
install -m644 /opt/prometheus/deploy/apps-silentmode-st.conf /etc/angie/http.d/
angie -t && systemctl reload angie
# systemd
install -m644 /opt/prometheus/deploy/prometheus-service.service /etc/systemd/system/
install -m644 /opt/prometheus/deploy/prometheus-snapshot.service /etc/systemd/system/
install -m644 /opt/prometheus/deploy/prometheus-snapshot.timer /etc/systemd/system/
# Instance-specific environment (NOT in the repo)
cat > /etc/default/prometheus <<EOF
ADMIN_PUBLISHER=<a BNS name you own>
# VIRUSTOTAL_API_KEY=<key> # optional
# PAYMENT_REQUIRED=1 # enable paid wave
# PROMETHEUS_PAYMENT_ADDRESS=<cashaddr> # required when PAYMENT_REQUIRED=1
# PROMETHEUS_LISTING_FEE_USD=1
EOF
chmod 600 /etc/default/prometheus
systemctl daemon-reload
systemctl enable --now prometheus-service.service
systemctl enable --now prometheus-snapshot.timer
# Verify
curl -k https://127.0.0.1/healthz # should return 200 and {ok:true,…}
Register the on-chain record (workstation)
IP=$(curl -s https://ifconfig.io) # or the VPS's public IP as you know it
TLS=<the fingerprint make-tls-cert.sh printed>
node Argus/src/register.js prometheus.x "{\"ip\":\"$IP\",\"tls\":\"$TLS\"}"
# Prompts for the chipnet keystore password (or set DEVIANT_KEYSTORE_PASSWORD).
The current record (as of 2026-10-08) is {"u":"https://silentmode.st/prometheus/"}.
The register command above replaces it. Within a few minutes of the TX
confirming on chipnet, Theseus and Ariadne resolve prometheus.x to the live
service rather than the silentmode.st teaser.
Updates
Code: rsync Prometheus/ again, npm install --omit=dev (safe no-op if deps
unchanged), systemctl restart prometheus-service.
Snapshot: nothing to do — the timer runs itself.
Cert rotation: re-run make-tls-cert.sh, grab the new fingerprint, re-register
the tls record, reload angie. Theseus and Ariadne pick up the new cert as
soon as the record TX confirms.
Rollback
Code: rsync the previous checkout, restart. There is no "schema down migration" discipline yet — the DB file is append-only in practice (new columns, new tables); if a rollback hits a schema change you have to decide what to do with the newer rows.
Record: node Argus/src/register.js prometheus.x '{"u":"https://silentmode.st/prometheus/"}'
puts the name back to redirecting at the ICANN mirror. Takes the same few
minutes as any other record change.