• URL: https://git.mammoth.com.au/vps/vps (project ID: 1)
• Namespace: vps group
• Default branch: main
• Description: All first-party software for BinaryLane / Mammoth Cloud services
• Access: Requires Mammoth WireGuard VPN + GitLab PAT
• API base: https://git.mammoth.com.au/api/v4/ (use –resolve git.mammoth.com.au:443:10.240.0.211 from this host)

The repo follows a two-level category/component/ structure:

vps/vps/
├── facility/         — Satellite services (per-datacentre, not core VPS)
│   ├── backupproxy   — .NET backup download proxy
│   ├── looking-glass — PHP BGP/traceroute tool (modified third-party)
│   └── rescueproxy   — .NET VNC access proxy
├── infrastructure/   — Physical device software (compute hosts, routers, switches)
│   ├── backup        — SSH-invoked backup scripts (called by HostDaemon)
│   ├── compute       — Programs deployed to compute host nodes
│   ├── dynamic-routing — Rust routing application
│   ├── gbmt          — ECC memory stress testing (memtester + geekbench)
│   ├── isobuilder    — ISO build tooling
│   ├── neigh-proxy   — NDP/ARP proxy
│   ├── qemu          — QEMU configuration/tooling
│   └── third-party   — Third-party integration code
├── ops/              — Service maintenance and operations
│   ├── ansible       — Ansible playbooks
│   ├── bitwarden-backup — Bitwarden backup automation
│   ├── butler        — Butler bot
│   ├── cicd          — CI/CD tooling
│   ├── icinga        — Monitoring
│   ├── morbo         — ???
│   ├── scripts       — Ops scripts
│   ├── tinydns2bind  — DNS conversion
│   ├── trello2gitlab — Migration tool
│   └── tron          — IPMI host interaction (Python)
├── product/          — Core customer-facing functionality
│   ├── base-image-test
│   ├── cli-based-tests — E2E tests against WebAPI
│   ├── e2e-tests
│   ├── forks         — Third-party forks with modifications
│   ├── guest-agent
│   ├── history
│   ├── mentos
│   ├── rat
│   ├── unused-code-remover
│   ├── vmbuilder       — VM image builder
│   └── website/      — Main .NET panel/API solution (see below)
├── team/             — Staff-only tools
└── scripts/          — General-purpose scripts

A separate repository for compute host-side programs:

vps/compute/
├── hostdaemon/       — Daemon on compute hosts
├── ovmf/             — UEFI firmware
├── power-limiter/    — Power management
├── qemu-network/     — iptables/netns firewall (see also vps/qemu-network)
├── routed/           — Routing daemon
├── scripts/          — Compute host scripts
├── services/         — Host services
├── smtbalance/       — SMTP balancing
├── xm/               — Xen configuration
├── xmconfig/         — Xen config tools
└── xm-for-kvm/       — Xen-to-KVM migration tools

Additional ops projects not in the main monorepo:

Third-party forks with modifications:

PAT=$(/root/.secrets/bw-get-secret.sh "Mammoth GitLab PAT" "pat")
 
# List group projects
curl -sk --resolve git.mammoth.com.au:443:10.240.0.211 \
  -H "PRIVATE-TOKEN: $PAT" \
  "https://git.mammoth.com.au/api/v4/groups/vps/projects?per_page=100"
 
# Read a file (base64-encoded content)
curl -sk --resolve git.mammoth.com.au:443:10.240.0.211 \
  -H "PRIVATE-TOKEN: $PAT" \
  "https://git.mammoth.com.au/api/v4/projects/22/repository/files/product%2Fwebsite%2FDomain%2FEntities%2FGuestFirewallRule.cs?ref=main"
 
# List directory tree
curl -sk --resolve git.mammoth.com.au:443:10.240.0.211 \
  -H "PRIVATE-TOKEN: $PAT" \
  "https://git.mammoth.com.au/api/v4/projects/22/repository/tree?path=&per_page=100"

• Monorepo migration is still a work-in-progress — some projects live in separate repos
• product/website/ is the main .NET solution (MammothVps.slnx)
• infrastructure/compute and vps/compute both contain compute host software
• vps/qemu-network (project 20) is separate from infrastructure/qemu and vps/compute/qemu-network
• Several projects are Rust-based (vps/ndp-responder-rs, vps/dynamic_rs)
• The vps/ops and vps/forks subgroups have their own GitLab groups with separate project IDs

• BinaryLane Architecture - Panels & Customer Entry Points
• Customer-Side Bug Finding Methodology