Infrastructure

Notes on running systems in production — containerization, deployment pipelines, monitoring, and the operational patterns that keep things stable.

---

Containerization & Docker

Practical patterns for running containers without fighting the tooling.

• Docker: Automatically Exiting Containers — why your container exits immediately and how to fix it
• Docker: Exec and Writing Results to a Variable — capturing command output from inside a container
• Docker Windows Tips & Tricks — Windows-specific gotchas and workflows
• Docker Network Issues — connectivity problems and how to diagnose them
• Install Chrome on Amazon Linux 2 Workspace — headless browser setup for automation
• Install Docker on Amazon Linux Workspace — quickstart for AL2 environments

Deployment & CI/CD

Pipeline patterns that keep deployments predictable and reversible.

• Host a Static Site Using Pelican, Amazon S3 — content-as-code publishing without a CMS
• Pelican Static Site: Continuous Delivery to AWS S3 — GitHub Actions workflow for automated deployment
• GitLab: Generate Release Notes — CI/CD — automated changelog generation
• Install Consul with Minikube, Helm, Docker — service discovery in Kubernetes

Observability & Monitoring

You can't fix what you can't see. These notes cover structured logging, metrics, and alerting patterns.

• Splunk: Quick Reference — core SPL queries and search patterns
• Splunk: Core Certified User — Certification Tips — what to focus on when studying
• New Relic: Quick Reference — APM basics and query syntax

Workspace & Dev Environment

Setting up reproducible development environments without losing time to config drift.

• Windows: WSL Reset Root Password — recovery when you lock yourself out
• Generate Bulk XML Files for Load Testing — Raven tool for middleware stress testing

---

Patterns Worth Remembering

Containers should fail fast. If a container exits immediately, it's usually a missing entrypoint command or a misconfigured health check. Fix the root cause, don't paper over it with sleep 3600.

Infrastructure as code isn't optional. If you're manually configuring servers, you're creating snowflakes. Codify everything, even if it feels like overkill today.

Observability is a feature, not an afterthought. Structured logging, metrics, and tracing aren't "nice to have" — they're what let you debug production at 2 AM without losing your mind.