docs: add pinky to server fleet map
Pinky was missing from the map entirely. Documents its purpose (Docker/Linux-only workloads, esp. Android SDK/emulator builds) and the current SSH access gap (root's key not authorized, user is malin) found while chasing an apuntiq Android build.
This commit is contained in:
@@ -19,13 +19,18 @@ whichever host you happen to already be connected to.
|
||||
| **gringo** | `100.95.46.79` (LAN `192.168.168.68`) | Internal apps/tools host — replacement for the old Linux Docker host barky-1 | ~45 Bastille VNET jails on `10.20.0.0/24` (APIs, dashboards, Gitea, analytics, productivity tools). Default-deny outbound pf model; NPM dedicated ports `8000 + last octet`. See `docs/server-gringo.md`. |
|
||||
| **zamolxis** | `100.115.128.41` | Standalone (non-jailed) FreeBSD site host | Not part of the granja/external-fleet jail families — a single site (Newspaper/tagDiv theme, PHP 8.5) running directly on the host, not in a jail. |
|
||||
| **cabrera** | `100.100.108.19`, SSH port `79` | External Linux affiliate-network host (BTPanel-style) | Part of the older Linux fleet (alongside raptor/maagar/formentor/moonie/spunky/proton/shoe — several since decommissioned/migrated to funky). Hosts easycut.es's main WooCommerce e-commerce site directly (not jailed). |
|
||||
| **pinky** | `100.78.228.127` (`pinky.taild32c88.ts.net`) | Linux/Docker-only workloads — genuine Docker containers, or a Linux-only build toolchain (the **Android SDK + emulator** for Capacitor APK builds, e.g. Bauxa) | Not part of the FreeBSD/Bastille fleet above — **SSH user is `malin`, not `root`**, and as of 2026-08-13 `root`'s standard key is not authorized here (`Permission denied (publickey)`; `tailscale ssh` also fails). No working credentials for this host as of that date — same blocker hit independently by two unrelated tasks (SMS gateway deploy, apuntiq Android build). Don't default work here just because it's Linux-flavored — see "How to decide" below; this host is for genuinely Docker/Linux-specific needs only. See `docs/server-pinky.md` in granja. |
|
||||
|
||||
## How to decide where new work belongs
|
||||
|
||||
1. **What kind of thing is it?** A corporate/internal tool → venus. A
|
||||
customer's production site → funky. A new affiliate-network travel
|
||||
site → granja. A quick experiment or something not ready for anything
|
||||
resembling production → staging.
|
||||
resembling production → staging. **Default to FreeBSD (gringo) even
|
||||
for Linux-shaped work** — only use pinky if it genuinely needs Docker
|
||||
or a Linux-only toolchain (e.g. the Android SDK/emulator); "it's
|
||||
Linux/Docker-based elsewhere in this project" is not by itself a
|
||||
reason to put a stateless piece on pinky.
|
||||
2. **Does it already have an established host from a related sibling
|
||||
project?** (e.g. another CloudHost-org first-party tool already lives
|
||||
on venus) — match that, don't scatter related things across hosts
|
||||
|
||||
Reference in New Issue
Block a user