Skip to content

Infrastructure Inventory

River Oaks Church - Created April 2026

This page began as an April 2026 source-derived inventory of the on-prem and adjacent infrastructure that makes River Oaks technology run. The dated live guest list below supersedes its April guest count; the service descriptions and open questions farther down remain historical until separately checked. Where a detail wasn't determinable from source, it is marked (unknown — confirm) in the Open Questions appendix.

This page is internal-only and lives behind the docs site's auth. Nothing on this page should be treated as a security boundary on its own.


Overview

  • Single Proxmox server at the River Oaks main campus (no cluster).
  • April 27, 2026 snapshot: 40 logical CPU cores, 49.43 TiB storage, 13 VMs online, 0 stopped, and 3 LXC containers. Utilization at that time: 68% RAM, 19% CPU, 44% storage. See the September 30 live guest list below for the current observed guest denominator; host capacity was not rechecked.
  • Internet: 1 Gbps fiber primary, 300 / 40 Mbps cable backup.
  • Network fabric: 10G backbone, Ubiquiti end-to-end ("pretty large" network for the site size). Plus a handful of Raspberry Pis on one-off tasks.
  • Cross-site connectivity to Cole's datacenter and home runs over a WireGuard mesh with FRR-OSPF routing terminated at a dedicated VPN-Node VM at the church. Some River-Oaks-owned VMs sit at the Beam Networks datacenter and ride that mesh in.
  • Public ingress: primarily nginx on rocc-db for *.ro.church apps, plus Cloudflare (Pages, Tunnels, Access) for some surfaces. See Cloudflare DNS and redirects for account/zone ownership and the Git change process.
  • Backups: Proxmox has configured local and gofer2 jobs, verified read-only on October 1, 2026. The separately documented Google Team Drive sync via LXC 109 was not reverified in that check. See VM Backups for schedules and verification limits.

The server itself is referred to as rocc01 in older notes (see Inventory home). The Proxmox web UI is at https://proxmox.1nine89.net (per the docs home page).


VMs and Containers

Live Proxmox guest snapshot — September 30, 2026

Read-only pvesh get /cluster/resources --type vm --output-format json on rocc01 (10.200.24.2) returned 25 running guests: 16 QEMU VMs and 9 LXC containers. The primary interface IPv4 values below were also checked on September 30 using the QEMU guest agent (VMs) or pct exec (LXCs). Multiple addresses are shown where the guest reported multiple primary interfaces; these are observations, not guaranteed service endpoints. VM 111's guest agent did not respond, so its address remains unverified. This is not yet a verified service, OS, ownership, backup, or IaC inventory.

VMID Proxmox label Type Status RAM (GiB) Observed primary IPv4
100 rocc-db VM running 8 10.200.24.42
101 mdf-companion VM running 4 10.200.24.41
102 cloudron VM running 8 10.200.24.53
103 mpr-nr VM running 8 10.0.40.12, 192.168.1.78
104 telegram-nr VM running 2 10.0.22.223
105 studio-nr VM running 2 10.0.40.15, 10.200.18.74
106 mdf-nr VM running 4 10.0.40.11
107 filebox VM running 2 10.200.24.40
108 video-companion VM running 4 10.200.24.46
109 storage-mgr LXC running 4 10.200.24.5
110 bitwarden VM running 4 10.200.24.36
111 ro-status VM running 4 (unverified — guest agent unavailable)
112 dns-1 VM running 2 10.200.200.200
113 wireguard-router VM running 4 10.1.1.22
114 ro-influxdb LXC running 2 10.200.24.3
115 ro-grafana LXC running 2 10.200.24.4
116 ro-youtube-dl LXC running 4 10.200.24.9
117 admin-ansible LXC running 2 10.200.24.48
118 ro-litellm LXC running 4 10.200.24.55
119 ro-authentik LXC running 4 10.200.24.13
120 ro-assistant LXC running 2 10.200.24.58
121 ro-openbao LXC running 1 10.200.24.59
122 cgood-dev VM running 16 10.200.17.17
123 aes67-recorder VM running 8 10.200.24.10
124 ro-ai-reviewer VM running 8 10.200.24.54

Deployment-target evidence — October 1, 2026

A read-only scan of riveroaks/infra main (f8570be) found declared deployment targets matching 10 of the 25 live guests by explicit VMID or by the guest's observed primary IPv4. Representative target files are linked below; some guests have additional targets in the same repository. This is repository coverage, not proof that the target was deployed, is healthy, owns the whole guest, or can recreate it. No exact target match in this repository was found for the other 15 guests; they may be managed from another repository or manually.

VMID Guest Matching riveroaks/infra target Match basis
100 rocc-db nginx/rocc-db.json observed IPv4
103 mpr-nr nodered/mpr.json VMID and IPv4
104 telegram-nr nodered/telegram.json VMID and IPv4
105 studio-nr nodered/studio.json observed IPv4
106 mdf-nr nodered/mdf.json VMID and IPv4
109 storage-mgr storage/storage-vm.json observed IPv4
115 ro-grafana observability/ro-grafana.json VMID and IPv4
116 ro-youtube-dl observability/ro-youtube-dl.json observed IPv4
121 ro-openbao secrets/openbao.json VMID and IPv4
124 ro-ai-reviewer ai-code-reviewer/ro-ai-reviewer.json VMID and label

The sections below are the original source-derived April 27 service notes. Their former 13-VM/3-LXC denominator and claims of unnamed guests are stale: all current guests have Proxmox labels, but many still need role, deployment-ownership, and backup-result verification before the inventory is complete. The observed IPv4 values above supersede older address guesses; for example, 10.200.24.36 belongs to VM 110 (bitwarden) in the live snapshot and must not be assumed to be the links backend.

rocc-db — webserver / DB / Node-RED / portal host

The single most loaded VM. Everything *.ro.church external lands here.

Field Value
Hostname rocc-db
IP 10.200.24.42
Proxmox VMID 100 (per backup policy in VM Backups)
OS Ubuntu (PHP 8.1, nginx, MySQL/MariaDB)
Role Public web tier + MySQL + Node-RED + portal stack
Public surface portal.ro.church, forms.ro.church, lyrics.ro.church, dev.portal.ro.church, ro.church (short links), *.gs.ro.church (Goshen wildcard), links.gs.ro.church, eugenecarol.com, forms.eugenecarol.com
Internal-only listeners nginx :1881 (Node-RED proxy), nginx :8080 (phpMyAdmin), nginx :8020 localhost-only (UniFi API helper), nginx :8123 TCP stream → 10.0.50.13:8123 (MQTT broker)
Services on host nginx, php8.1-fpm, MySQL/MariaDB, Node-RED (PM2), local certbot, GitLab CI runner ro-portal-1
Auto-deploy nginx is wired through infra repo's deploy:nginx:rocc-db GitLab job (manual on main); portal deploys via riveroaks/portal CI on push to main / dev
Owner Cole (primary)

Notes pulled from source:

  • The repo riveroaks/infra/nginx/hosts/rocc-db/ is a one-to-one mirror of /etc/nginx/ on this VM. Top-level nginx.conf defines a map $host $backend_endpoint for *.gs.ro.church proxying and a stream listener on :8123.
  • The Node-RED runtime at ~/.node-red/ (PM2 app node-red) listens on :1880; nginx proxies :1881 to localhost:1880. Custom palette has 23 node-red-contrib-* modules (see infra/nodered/instances/rocc-db-local/package.json).
  • The portal mounts at /usr/share/nginx/portal/{dashboard,forms,lyrics,errors,unifiapi}/. The dev portal mounts at /usr/share/nginx/html/dev-portal/dashboard/.
  • TLS: wildcard cert for gs.ro.church lives at /home/riveroaks/local-certbot/certbot/conf/live/gs.ro.church/. The *.ro.church chain is presumed managed elsewhere (unknown — confirm).

Reload: sudo nginx -t && sudo systemctl reload nginx. Node-RED: pm2 restart node-red (run via the user nvm PATH).

bitwarden — Bitwarden / Vaultwarden VM

Field Value
Hostname (unknown — confirm; called "Bitwarden" in backup policy)
Proxmox VMID 110 (high-frequency backup tier per VM Backups)
Role Self-hosted password manager for IT credentials
Public surface (unknown — confirm) — referenced as the credential store of record across the IT docs
Owner Cole (primary)

storage-mgr — backup orchestrator (LXC 109)

Field Value
Container ID 109 (LXC)
Role Drives nightly rclone push of Proxmox backups to Google Team Drive
Mounts /mnt/proxmox-backups (read-only bind from host's /var/lib/vz/dump)
Cron 0 0 * * * /root/proxmox-backup-sync.sh — weekly snapshot, 13-week retention
Excluded from local backup jobs yes, to avoid recursion

Documented at VM Backups.

ro-ntfy — Ntfy notifications gateway

Field Value
Hostname ro-ntfy (called out by name in Ntfy Account Setup)
IP (unknown — confirm)
Role Alert/notification fan-out for IT
Public surface notifications.ro.church

Per IT Notifications, the Ntfy service is described as currently hosted at the datacenter. The user-add procedure (Ntfy Account Setup) tells operators to log into Proxmox and find a VM named ro-ntfy, which suggests an on-prem VM exists — (confirm: is ro-ntfy on-prem at RO, at the datacenter, or both?). The October 1 datacenter snapshot below shows an RO-pool VM 146 labeled ntfy; there is no ro-ntfy label among the 25 running rocc01 guests. Whether VM 146 serves notifications.ro.church still needs a service check.

billionmail — MailerSend dynamic-template substitute

Field Value
Hostname (unknown — confirm; service name "BillionMail")
IP 10.141.74.109
Role Self-hosted dynamic email templating; receives traffic from db-nodered
Where it actually runs today datacenter (per Goodbye SendGrid, with a stated plan to move it to the church)

Lives on the same VLAN as the rest of the RO VMs at the datacenter, so RO can reach it via the OSPF mesh through the static route to the datacenter. Listed here because it is a River-Oaks-owned VM even though it is currently parked at the BN datacenter.

Goshen-campus Node-RED VMs (mpr-nr, youth-nr, tech-nr)

Three Node-RED runtimes referenced by the map $host $backend_endpoint block in rocc-db's nginx.conf:

Hostname (vhost) Backend
mpr-nr.gs.ro.church 172.16.64.24:1880
youth-nr.gs.ro.church 172.16.64.25:1880
tech-nr.gs.ro.church 172.16.64.26:1880

All three are reverse-proxied via the *.gs.ro.church wildcard vhost on rocc-db, with WebSocket upgrade headers preserved. They sit on the Goshen campus VLAN (172.16.64.0/24). Whether each is its own VM, its own LXC, or all on one Proxmox host at the Goshen campus is (unknown — confirm).

These are retained as historical inventory entries. The currently migrated River Oaks fleet is listed in Node-RED runtimes (RO side) below; do not assume these legacy Goshen names are part of that fleet without confirming their current callers and backends.

DB Node-RED — migrated primary RO Node-RED

Field Value
Hostname / FQDN Canonical editor: db.nodered.riveroaks.cc; compatibility: db-nr.riveroaks.cc; legacy DNS: db.nodered.ro.church
Where it runs rocc-db (10.200.24.42), target name rocc-db-local
Role Webhook target for the portal — login events, WiFi signups, key fob requests, account creation, email send-out
Talked to by riveroaks/portal; existing Portal/webhook/automation callers through /public/...
Authentication Authentik OIDC for editor routes; IT group only
Source of truth riveroaks/infra/nodered/instances/rocc-db-local/ and deploy/targets/nodered/rocc-db-local.json
Owner River Oaks IT

The Portal's active callers were migrated to the canonical .nodered.riveroaks.cc names. The /public route remains intentionally unauthenticated for machine callers; the editor and administrative routes require Authentik. See Node-RED: Authentik, URLs, and IaC for the fleet-wide workflow and compatibility policy.

links.gs.ro.church backend

Field Value
Hostname (unknown — confirm)
IP / Port 10.200.24.36:3000 (per nginx vhost in infra/nginx/hosts/rocc-db/sites-enabled/gs.ro.church.conf)
Role Goshen short-link service
Public surface links.gs.ro.church

10.200.24.36 is one octet off from rocc-db (.42), suggesting a sibling VM in the same 10.200.24.0/24 subnet. Possibly the YOURLS or similar URL-shortener stack.

Cluster of unidentified VMs in 10.200.24.0/24 and 10.200.25.0/24

Two additional surfaces visible from configs but not yet documented:

  • 10.0.50.13:8123 — TCP stream proxy target from rocc-db's nginx (stream { server { listen 8123; proxy_pass 10.0.50.13:8123 } }). Cross-referenced as the MQTT broker address used by Node-RED flows (per infra/nodered/instances/rocc-db-local/flows.json line 643). (confirm host — could be at the datacenter on the OSPF mesh given the 10.0.x.x prefix, or could be a homelab address routed in.)
  • 10.200.25.155 and 10.200.25.156 on TCP 12445 — Two-NVR UniFi Access cluster ("stacked NVRs" per the Door Access home page). Hardware appliances, not Proxmox VMs. Termination for door-control and key-fob enforcement.

Live datacenter RO-pool guest snapshot — October 1, 2026

A read-only pvesh get /cluster/resources --type vm query on the Beam datacenter cluster, filtered to pool RO, returned 14 guests: 13 running and one stopped. Addresses were checked the same day via QEMU guest-agent network metadata or pct exec for LXCs. Only observed primary/routed IPv4 addresses are shown; container bridge addresses are omitted. VM 156 has a br-billionmail interface at 172.66.1.1, but that bridge name alone does not verify an active BillionMail service or the historical 10.141.74.109 address. VMs 136, 146 and 155 had no running guest agent; stopped VM 191 has no observed runtime IP. Pool membership and these addresses do not verify service roles, IaC, backups or application health. Other River Oaks-owned workloads outside pool RO may exist and are not silently included. These guests are River Oaks inventory, not Beam-owned targets for bulk operations.

VMID Proxmox label Type Node State Observed IPv4
136 web1 VM px5 running (unverified — guest agent unavailable)
137 docs VM px5 running 10.141.70.102
139 ro-rad1 VM px2 running 10.141.74.100
140 ro-rad2 VM px5 running 10.141.74.101
141 ro-rad3 VM px4 running 10.141.74.102
144 ro-status VM px3 running 10.141.74.108, 172.16.64.86
146 ntfy VM px5 running (unverified — guest agent unavailable)
151 ro-mkdocs-runner1 LXC dev1 running 10.141.74.105
153 ro-portal-runner1 LXC px4 running 10.141.74.115
155 dns02 VM px5 running (unverified — guest agent unavailable)
156 ro-mail VM px3 running 10.141.74.114
168 riveroaks.org VM px1 running 10.141.74.111
182 ro-au-rtr VM px1 running 10.141.74.2, 172.16.65.2
191 web2 VM ai1 stopped (not observed — stopped)

The cluster has an enabled pool-RO snapshot job backup-7a84231e-af56 targeting gofer-9-pbs on its configured mon,fri,sat 08:00 schedule. On October 1, a read-only PBS catalog query for each of the 14 VMIDs above found four snapshots per guest, with the newest snapshot for every guest dated September 28, 2026 (approximately 12:00 UTC, including stopped VM 191). This verifies catalog presence and scheduled selection as of that date, not backup content integrity, offsite replication, an application-consistent restore, or the result of the next scheduled run. Keep restore evidence separate from this inventory.

Historical datacenter-side service notes

Several of the IPs that show up in portal source live in the 10.141.x.x and 172.19.x.x ranges, which belong to RO-owned VMs hosted on the BN datacenter cluster (the trust-boundary exception called out in Team/_SharedMemory/reference_infrastructure_topology_and_capacity.md). The ones identified by name:

Service Address Identified from
BillionMail 10.141.74.109 is historical; VM 156 ro-mail has an observed br-billionmail bridge and primary IPv4 10.141.74.114, but the service endpoint is not verified Goodbye SendGrid and read-only guest-agent interface metadata
RAD1 / RAD2 / RAD3 (FreeRADIUS) Guest-agent IPv4: 10.141.74.100, .101, .102; service role still to verify RADIUS Troubleshooting — historical service note; live VMIDs 139/140/141 above

These are documented under the River Oaks side because they're RO-owned even though they're physically at the BN datacenter — this matches the trust-boundary policy.

Historical on-prem count (superseded)

The April estimate of 13 VMs + 3 LXCs and 8–9 unnamed guests is superseded by the September 30 live 25-guest table above. All those guests have Proxmox labels; role, ownership, IaC and recovery verification remains.


Services not on a dedicated VM

MySQL / MariaDB

Lives on rocc-db (localhost) and is the database for the entire portal monorepo. Three databases are in active use:

  • public — primary portal database (users, key fobs, networks, logs, vars).
  • tickets — IT/maintenance tickets.
  • expense_forms — March 2026 expense-request app, plus line items, attachments, and audit events.

A fourth database (logs) is referenced in dashboard/static/config.php.

Connection details are loaded from dashboard/static/config.php and the root .env (for the expense flow). MySQL is localhost-only on rocc-db; no external listener.

This is the RO MySQL host. It is separate from Beam's au-db.cg-e.net:6033 instance — see Team/_SharedMemory/reference_mysql_hosts.md. RO never connects to au-db; Beam never connects to this one.

Node-RED runtimes (RO side)

Five active instances are currently managed by the River Oaks IaC workflow. The older Goshen names below remain in the historical inventory and should not be retired until their callers and backends are separately confirmed.

Instance Where Notes
studio Studio Node-RED VM studio.nodered.riveroaks.cc; Authentik OIDC; Git/IaC-managed.
mpr MPR Node-RED VM mpr.nodered.riveroaks.cc; Authentik OIDC; Git/IaC-managed.
mdf MDF Node-RED VM mdf.nodered.riveroaks.cc; Authentik OIDC; Git/IaC-managed.
telegram Telegram Node-RED VM telegram.nodered.riveroaks.cc; Authentik OIDC; Git/IaC-managed.
rocc-db-local rocc-db (10.200.24.42:1880, proxied via nginx) db.nodered.riveroaks.cc; Authentik OIDC for editors, /public retained for machine callers.

Five identified; 0–5 more (unknown — confirm).

rocc-db-local's flow file references the MQTT broker at 10.0.50.13:8123 and an external auth-event SQL flow that writes to a nr-user-access table. Several flows POST to UniFi Access NVRs at 10.200.25.155 / 10.200.25.156.

For the deployment workflow, compatibility aliases, and rollback details, see Node-RED: Authentik, URLs, and IaC.

Snipe-IT (asset tracking)

Field Value
Public surface inventory.ro.church
Where "Snipe-IT is ran in a Docker hosting software called Cloudron. The Cloudron VM is ran on rocc01." (per Inventory home)
Owner Cole / RO IT

This is a separate Snipe-IT instance from Beam Networks' Snipe-IT (per Team/_SharedMemory/reference_snipe_it_inventory.md). Data does not federate.

Documentation site (this site)

Field Value
Public surface docs.ro.church (auth-protected)
Build MkDocs (Material theme) — mkdocs build && wrangler pages deploy site/
Hosting Cloudflare Pages (project ro-docs) — see riveroaks/docs/.gitlab-ci.yml
CI runner ro-docker-1
Repo git-local.beamnetworks.cloud:riveroaks/docs.git, branch main

Note: the page Documentation Site Hosting currently says the site runs on Cole's Proxmox cluster at the datacenter — that is out of date as of 2026-04. The CI definition deploys to Cloudflare Pages now. Worth a follow-up edit when convenient.

UniFi Network Controller

Field Value
Internal endpoint https://10.100.1.58 (per portal README.md, "External Integrations")
Where UDM / NVR appliance, not a VM
Role Manages WiFi WLANs and access groups on the campus network
Used by portal's UniFi API client for WiFi WLAN management

UniFi Access (door / key fob)

Field Value
Internal endpoints https://10.200.25.155:12445, https://10.200.25.156:12445
Where "stacked NVRs" — hardware appliances at the church
Role Door access control + key-fob enforcement
Used by portal key-fob flow + Node-RED flows that grant/revoke user-group membership

UISP (PTP wireless)

Field Value
Public surface uisp.beamnetworks.dev
Where Hosted at Beam Networks' datacenter, not at RO (per UISP Hosting)
Role Manage Ubiquiti PTP wireless links between buildings

Out of scope for this RO inventory but documented here because the existing docs page already calls it out.

ProPresenter

Field Value
Internal endpoint http://10.200.5.5:1025/v1/
Where Sanctuary control PC (not on Proxmox)
Role Source of slide / lyric data for lyrics.ro.church
Polled by lyrics/poll_propresenter.php on rocc-db (every 50 ms; cached to /dev/shm)

Status monitoring (Uptime Kuma)

Field Value
Public surface status.ro.church (editor: /dashboard; public: /status/network)
Where "Docker running on the Oracle VM in the cloud" (per Network Monitoring)
Role Pings VMs and devices to track uptime

Cloud-hosted (Oracle Free Tier), not on RO Proxmox.

Other off-prem RO surfaces

For completeness — these are accessible via the docs landing page and exist outside the RO server:

  • portal.ro.church / dev.portal.ro.church — same rocc-db VM; listed here because they're the most-used surface.
  • Cloudflare account — account and zone configuration is code in riveroaks/cloudflare-infra; use the Cloudflare DNS and redirects runbook. Do not edit managed resources in the dashboard. Pages/app resources keep their documented repository owners.
  • Jamf Cloud (riveroaks.jamfcloud.com) — Apple device management. SaaS, not on-prem.
  • Jamf Protect (riveroaks.protect.jamfcloud.com) — SaaS.
  • GitLab (gitlab.au.bncorp.dev) — code repository and CI/CD.
  • Proxmox UIs — proxmox.1nine89.net (RO on-prem), px-prod.beam-hosting.net (Cole's datacenter where some RO VMs also live).

Network Fabric

IP plan (as inferred from configs)

Range Where Notes
10.200.5.0/24 RO main campus — sanctuary AV ProPresenter (10.200.5.5)
10.200.24.0/24 RO main campus — server VLAN rocc-db (.42); links backend (.36)
10.200.25.0/24 RO main campus — UniFi Access NVRs .155, .156
10.100.1.0/24 RO main campus — UniFi Network controller 10.100.1.58
172.16.64.0/24 Goshen campus VLAN UniFi Network at .10; Node-RED VMs at .24/.25/.26; client devices .131 example
10.0.50.0/24 (unknown — confirm) — possibly home or DC MQTT broker at 10.0.50.13:8123
10.141.70.0/24, 10.141.74.0/24 RO VMs at the BN datacenter BillionMail at 10.141.74.109
172.19.x.x RO VMs at the BN datacenter (RADIUS subnet, etc.) RAD1/RAD2/RAD3 likely live here

VLAN map (unknown — confirm)

We don't have a complete VLAN list in source. What we do know:

  • Goshen campus has its own VLAN that maps to the 172.16.64.0/24 IP space.
  • RO main campus has at minimum a server VLAN (10.200.24.x), an AV VLAN (10.200.5.x), an Access-NVR VLAN (10.200.25.x), and a UniFi Network management surface (10.100.1.x).
  • IoT network exists per RADIUS Troubleshooting (Type 2 MAC-based accounts).

OSPF / WireGuard mesh

  • A dedicated VPN-Node VM at RO terminates the WireGuard mesh and runs FRR speaking OSPF to peers at home and the BN datacenter.
  • Cross-site reachability is via 10.x.x.x addresses; no public DNS bounce required for internal traffic.
  • Trust boundary: River Oaks cannot initiate connections into Beam Networks infra. RO-owned VMs that physically live at the BN datacenter (BillionMail, RADIUS, etc.) are the exception — they're already inside the BN edge.
  • Beam → RO outbound is unrestricted.
  • (unknown — confirm: VPN-Node hostname / VMID at RO.)

ISPs and public IP

  • Primary ISP: 1 Gbps fiber (provider: (unknown — confirm; "Surf" appears in Goodbye SendGrid as a potential public-IP source)).
  • Backup ISP: 300 / 40 Mbps cable.
  • Public IP allocation: single publicly-routable IP per site per the portfolio infrastructure note. Specific addresses (unknown — confirm).
  • Both ISPs are wired into the FRR-OSPF ring.

Public ingress

  • nginx on rocc-db is the primary public ingress for *.ro.church and the Goshen-wildcard vhosts.
  • Cloudflare sits in front for DNS, WAF, and Access-protected surfaces (e.g., this docs site, the Proxmox UI gating).
  • Cloudflare Tunnels are used in addition to nginx, but secondary to nginx as the primary path.

Backbone

  • 10G SFP+ Ubiquiti backbone.
  • Switch model / firewall make (unknown — confirm at RO; OPNsense is the firewall at the BN datacenter, not necessarily here.)

Trust boundaries with Beam Networks

Pulled from Team/_SharedMemory/reference_infrastructure_topology_and_capacity.md:

  • RO can NOT initiate new connections into BN infra (firewall posture).
  • RO-owned VMs at the BN datacenter are exempt — they're already inside BN's edge. BillionMail, RAD1/2/3, possibly Ntfy fall in this bucket.
  • BN → RO is unrestricted.
  • Per-environment isolation rules:
  • RO Node-RED ↔ BN Node-RED: never crosses. Five+ instances on each side, completely separate (per reference_node_red_topology.md).
  • RO MySQL on rocc-db is never queried by BN-side code; BN's au-db.cg-e.net:6033 is never queried by RO code (per reference_mysql_hosts.md).
  • RO Snipe-IT and BN Snipe-IT do not federate.

Open Questions

The following items are (unknown — confirm with Cole) and would close the gaps in this inventory. None of them are blocking; this is the backlog for a follow-up pass once a human can answer.

Per-VM gaps

  1. All 25 currently running guests now have VMID, Proxmox label, type, and observed primary IPv4 above (except VM 111's unverified IP). Match each guest to its current service role, owner, IaC source, and backup results; the April estimate of 8–9 unnamed VMs is obsolete.
  2. All nine currently running LXC containers are named in the live table. Confirm their current services and management sources; the April estimate of two unnamed containers is obsolete.
  3. bitwarden VM 110 — observed IP is 10.200.24.36; confirm its current public surface and service implementation.
  4. ro-ntfy VM — confirmed location: on-prem RO, at BN datacenter, or both? IT docs hint at both at different times.
  5. db.nodered.ro.church (edit.db.nodered.ro.church) — which host runs it? Is it a separate VM or another runtime on rocc-db?
  6. links.gs.ro.church backend — the April 10.200.24.36:3000 claim conflicts with VM 110's observed address. Verify the current upstream from live nginx config before assigning a VM or software role.
  7. 10.0.50.13 MQTT broker — host name, location (RO on-prem? home? DC?), what subscribes to it.

Network-fabric gaps

  1. Full VLAN list for the RO main campus — IDs, names, IP ranges, which are routed vs. isolated.
  2. Public IP addresses (primary + backup ISP) for the RO site.
  3. Primary fiber ISP name (Surf? something else?).
  4. VPN-Node VM — VM 113 is labeled wireguard-router in the live snapshot; verify that it is the documented VPN-Node and inventory its actual peers before treating the roles as identical.
  5. TLS chain for *.ro.church — is it ACME on rocc-db, ACME at the edge in Cloudflare, or a wildcard issued elsewhere?
  6. Firewall make / model for the RO main campus (is it OPNsense, Ubiquiti UDM Pro, something else?).

Datacenter-side RO VMs

  1. Active service roles for datacenter RO-pool VMIDs 139/140/141 (ro-rad1/2/3); their guest-agent IPv4 addresses are now observed above, superseding the historical 172.19.x.x guess.
  2. Datacenter RO-pool guests are named in the live 14-row snapshot. Verify their IPs, roles, IaC and backups, and determine whether other River Oaks-owned guests (including historical BillionMail) sit outside pool RO.

Service-level gaps

  1. Does rocc-db MySQL replicate anywhere? Or is it single-instance with backups only?
  2. ProPresenter VM — is 10.200.5.5 a Proxmox VM, a physical Mac/PC in the sanctuary, or both?
  3. Lyrics WebSocket process — currently described in portal docs as "must be started as a background process separately." Is it a systemd unit, a tmux session, a PM2 app, or something else? On rocc-db?
  4. Update docs-hosting.md — currently says the docs site runs on Proxmox at the datacenter. Reality (per .gitlab-ci.yml) is Cloudflare Pages. Worth a small PR.

Process-level

  1. Is there a documented mapping between gs.ro.church and the Goshen campus? This page assumes Goshen, but no docs site page explicitly says so.
  2. What runs on the Raspberry Pis "doing one-off tasks" at RO? Worth a short paragraph each if any of them serves traffic.

Appendix: source-file index

Files used to build this inventory (read-only). Listed for traceability so the next pass can regenerate cleanly.

From riveroaks/infra/:

  • README.md, roadmap.md, user-actions.md
  • nginx/hosts/rocc-db/README.md
  • nginx/hosts/rocc-db/nginx.conf
  • nginx/hosts/rocc-db/sites-enabled/*.conf (7 files)
  • nginx/hosts/rocc-db/sites-available/default
  • nodered/instances/rocc-db-local/README.md
  • nodered/instances/rocc-db-local/package.json
  • nodered/instances/rocc-db-local/flows.json (name only — contents contain auth tokens; not parsed in this inventory)
  • deploy/targets/nginx/rocc-db.json
  • deploy/targets/nodered/rocc-db-local.json
  • docs/inventory/nginx-hosts.md
  • docs/inventory/nodered-instances.md
  • docs/deploy/certificates.md
  • docs/deploy/gitlab-ci.md
  • .gitlab-ci.yml

From riveroaks/portal/:

  • README.md
  • dashboard/static/config.php (IP/host references only — no secrets read)
  • dashboard/v1.1/keys/config/unifi_api_config.php (IP/host references only)
  • dashboard/v1.1/keys/config/unifi_door_logs.php (IP/host references only)
  • dashboard/v1.1/tickets/trigger_email_service.php (IP/host references only)
  • lyrics/poll_propresenter.php (IP/host references only)
  • .env.example (template only)

From this docs site (riveroaks/docs/docs/):

  • index.md, IT/.nav.yml
  • IT/vm-backups.md, IT/vm-mainteance.md, IT/docs-hosting.md
  • IT/Inventory/home.md
  • IT/Networking/radius-troubleshooting.md
  • IT/Networking/status-monitoring.md
  • IT/Networking/uisp-manager.md
  • IT/Networking/ntfy-setup.md
  • IT/Networking/goodbye-sendgrid.md
  • IT/Networking/Doors/home.md
  • IT/Onboarding/notifications.md

From shared team memory (Team/_SharedMemory/):

  • reference_infrastructure_topology_and_capacity.md
  • reference_node_red_topology.md
  • reference_mysql_hosts.md
  • reference_snipe_it_inventory.md

No .env, .secret, credential, or private-key file was opened in producing this inventory.