rdb-discovery/context/infrastructure-context.md

/context/infrastructure-context.md

RDB Solutions Ltd Infrastructure Context

Physical Machines

Proxmox Server

Purpose:

• Main virtualisation host
• Runs infrastructure services and VMs/LXCs

Current known services:

• AdGuard
• Jenkins
• Nginx Proxy Manager
• Supabase VM
• Potential future OpenHands runner

Current constraint:

• Proxmox host currently has 16 GB RAM, so resource allocation should be conservative.

Preferred usage:

• Infrastructure services
• CI/CD
• Reverse proxy
• Databases
• Lightweight agent runners
• Isolated test environments

LLM / Ollama Machine

Hardware:

• NVIDIA RTX 5070 Ti with 16 GB VRAM
• 32 GB RAM

Purpose:

• Hosts Ollama
• Runs local LLMs such as Qwen
• Provides local model inference for development assistants and agent tooling

Preferred usage:

• Local coding models
• Agent backend model provider
• OpenWebUI integration
• Possible API endpoint for tools like Claude Code-compatible wrappers or OpenHands

MacBook Pro Intel

Purpose:

• Main development workstation

Preferred usage:

• IDE work
• Local coding
• Git commits
• Testing frontend/mobile apps
• Managing repositories and project files

Mini PC

Purpose:

• Hosts OpenWebUI
• Points to the Ollama machine for local LLM access

Preferred usage:

• Browser-based LLM interface
• Local AI assistant access
• Shared AI UI across the network

Virtual Machines and Containers

Jenkins

Purpose:

• CI/CD automation
• Build pipelines
• Test execution
• Deployment workflows

Preferred future use:

• Pull code from Gitea
• Build Docker images
• Run tests
• Deploy to hosted or self-hosted targets

Gitea

Purpose:

• Self-hosted Git server
• Source code control
• Replacement for Bitbucket/GitHub where possible

Preferences:

• Use Gitea as the source of truth
• Avoid GitHub-specific assumptions
• Use issues, milestones, and pull requests where useful

Supabase VM

Purpose:

• Database backend
• Postgres services
• Possible authentication/storage/API support depending on project needs

Preferred use:

• Application database
• Internal APIs
• Development/staging database
• Storage where suitable

Nginx Proxy Manager

Purpose:

• Reverse proxy
• SSL termination
• Routing internal services to friendly hostnames

Preferred use:

• Route apps and tools through internal domains
• Manage certificates
• Avoid exposing unnecessary services directly

AdGuard

Purpose:

• DNS filtering
• Local DNS support
• Network-wide ad/tracker blocking

Potential use:

• Internal DNS names for services
• Easier access to tools like Gitea, Jenkins, OpenWebUI, Supabase, etc.

LLM and Agent Architecture

RDB Solutions Ltd is interested in using local LLMs and coding agents to improve productivity.

Candidate tools:

• Ollama
• Qwen models
• OpenWebUI
• OpenHands
• Claude Code-style workflows pointed at local models where possible
• IDE assistants
• Task/backlog-driven development agents

Important preference:

• Agents should work from clear task files, context files, and isolated environments.
• Agents should not make broad uncontrolled changes.
• Agents should be able to run in a VM, LXC, or Docker container depending on risk level.

Recommended Isolation Model

For autonomous coding agents:

Preferred:

• Dedicated VM or LXC on Proxmox
• Access only to required repositories
• Limited credentials
• Network access restricted where possible
• Disposable working directories
• Git-based review before merge

Avoid:

• Giving agents unrestricted access to the main development machine
• Giving agents broad production credentials
• Allowing agents to directly deploy without review