Compute
Server hardware provides the foundation for storage, applications, containers, and supporting services.
← Back to Projects
Infrastructure
Enterprise Infrastructure Lab
A long-running hands-on environment for storage, Linux, containers, networking, self-hosted services, troubleshooting, permissions, recovery, and infrastructure administration.
TrueNASZFSLinuxDockerNetworkingStorageContainersRecovery
Overview
Infrastructure I Can Break and Rebuild
The infrastructure lab gives me a place to work with storage, networking, Linux, containers, services, and recovery without relying only on theoretical exercises.
It has evolved over time through hardware changes, storage migrations, application failures, permissions issues, networking problems, and experiments with different self-hosted services.
The value of the lab is not any single application. It is the experience of operating an environment where multiple systems depend on one another and failures have to be diagnosed across layers.
Architecture
Systems Working Together
Storage
ZFS-based storage provides pooled capacity, data organization, snapshots, and a foundation for recovery planning.
Services
Applications and containers run as managed services instead of being tied directly to a desktop environment.
Network
The lab connects storage, clients, media services, servers, and remote-management workflows across the network.
Hands-On Work
Operating the Lab
The environment is useful because it contains real services and real dependencies that need to be maintained.
TrueNAS & ZFS
Storage pools, datasets, permissions, capacity management, and ongoing administration.
Containers
Containerized services provide isolated and repeatable application environments.
Media Services
Self-hosted services provide practical workloads for storage, networking, transcoding, and permissions testing.
Linux Administration
Command-line administration, service management, troubleshooting, permissions, and system configuration.
Networking
High-speed connectivity, addressing, remote access, and ongoing segmentation planning.
Recovery
Snapshots, documentation, troubleshooting, and rebuild thinking are treated as part of system design.
Operations
Failure Is Part of the Lab
The most useful infrastructure lessons often come from the moments when services fail, permissions break, storage behaves unexpectedly, or networking does not work the way it should.
Permissions
Diagnosing file, dataset, application, and service access when users or containers cannot reach expected resources.
Storage
Working through capacity, pool behavior, datasets, application storage, and the consequences of configuration changes.
Applications
Troubleshooting services that fail to start, restart unexpectedly, lose access, or behave differently after updates.
Networking
Separating addressing, routing, DNS, service availability, and remote-access issues when connectivity fails.
Containers
Working through service configuration, volumes, permissions, dependencies, and container-level failures.
Recovery
Documenting changes and maintaining a rebuild mindset so individual services are recoverable rather than mysterious.
Lessons Learned
Infrastructure Is About Dependencies
01
A service failure may actually originate in storage, networking, permissions, or another dependency.
02
Documentation becomes more valuable as an environment becomes more complex.
03
Recovery should be considered while building a service, not after it fails.
04
Simple, understandable infrastructure is easier to operate than unnecessary complexity.
Direction
Where the Lab Goes Next
01
Improve network segmentation
02
Expand infrastructure monitoring
03
Strengthen documentation and recovery workflows
04
Build more repeatable container deployments
05
Integrate additional security controls
More Projects