This site
The page you're reading. I built it to show my homelab work, and used it to learn git, GitHub Pages and DNS for a domain I own.
- Stack
- Plain HTML and one CSS file, no framework or build step
- Hosting
- GitHub Pages, deployed on every push to
main - Domain
- Subdomain of techwizardsaz.com, DNS in AWS Route 53
- Source
- github.com/FutureITWizardFrank/portfolio
How it's built
- Simple on purpose. Static pages with light and dark themes that work on a phone. There is no server software to patch.
- Git workflow. I edit locally, preview with a one-line Python web server, then commit and push. GitHub Pages publishes the change in about a minute.
- Custom domain. A CNAME record in Route 53 points the subdomain at GitHub Pages, and GitHub issues the HTTPS certificate. The root domain stays free for a future business site.
- DNS troubleshooting. When GitHub's DNS check failed, I used
digagainst public resolvers to trace it to a missing record in Route 53. After I added it, my own Pi-hole was still caching the old "doesn't exist" answer.
Keeping it public-safe
- Example configs use made-up addresses and generic names. No real IPs, hostnames or camera locations.
- Secrets live in environment variables or uncommitted files, never in the repository.
- Commits use GitHub's private noreply email. I reset the history once so early drafts with more detail are gone.