About this environment
The platform is a non-commercial laboratory and learning environment run by a systems integrator working in enterprise content management. Its purpose is to build, operate and maintain the same classes of systems found in professional data center environments — hypervisors, virtual machines, containers, relational databases, monitoring and structured documentation — at a scale that fits a single administrator.
Everything published here is descriptive. No accounts, applications or services are offered to visitors from this page. Internal systems are operated on private network segments and are not exposed through this website.
Architecture
Virtualization
A Proxmox Virtual Environment cluster provides the hypervisor layer. Workloads run as KVM virtual machines and LXC containers, with scheduled backups and versioned host configuration.
Containerization
Application services are packaged as Docker containers, deployed through Portainer and defined as declarative Compose files so that each service can be rebuilt from source configuration.
Networking
The network is segmented into VLANs with dedicated routing and firewall policies. A reverse proxy terminates TLS and routes requests to the correct backend service by hostname.
Data and storage
Relational databases and network attached storage hold application state. Maintenance covers indexing, integrity checks, retention policies and tested restores rather than backups alone.
Operating practices
- Documentation first. Every host, service and recurring procedure is described in a self-hosted documentation system, so that a system can be rebuilt from written instructions.
- Automated certificate management. Transport encryption uses certificates issued and renewed automatically through the ACME protocol.
- Infrastructure as code. Configuration is generated by idempotent scripts; manual changes made directly on a host are treated as defects to be folded back into the scripts.
- Monitoring and alerting. Availability, resource usage and backup results are collected centrally and alert on deviation.
- Least privilege. Administrative interfaces are reachable only from internal network segments, with separate credentials per service.
Topics covered
- Server administration
- Linux and Windows Server operation, patch management, service configuration and troubleshooting.
- Database administration
- Schema migrations, query tuning, maintenance plans and backup verification.
- Network engineering
- Routing, VLAN design, DNS resolution, DHCP scopes and wireless infrastructure.
- Home and building automation
- Sensor integration, event-driven automation rules and local-first control systems.
- Documentation and knowledge management
- Structured technical writing, runbooks and change history for a small operations environment.
Technology stack
Domain usage
The apex domain nxus.sh serves this static informational page only. Subdomains resolve to
private address space and are used exclusively for internal administration from within the operator's own
network. There is no public login, no user registration, no file sharing and no advertising on this
domain.