Repurposing a dead-battery laptop into a self-hosted Linux server. This is the foundation everything else on this site runs on. Documented here using a real project management framework, not just a how-to.
Why this project exists, and what "done" looks like.
Having transitioned into ICT study after a decade in outdoor education, I found myself feeling behind my classmates, most of whom are a younger generation. This project converts an old laptop into a self-hosted Linux server: a low-cost, hands-on platform to build real skills in networking, sysadmin work, and web hosting through my own projects, rather than coursework alone.
What's included in this project, and what deliberately isn't.
| Boundary | Item |
|---|---|
| IN SCOPE | Wipe existing OS, install Linux Mint |
| IN SCOPE | Configure the laptop as a functioning server |
| IN SCOPE | Install & configure Nginx to host content |
| IN SCOPE | Solve remote access under CGNAT via Cloudflare Tunnel + domain |
| OUT OF SCOPE | Purchasing new hardware |
| OUT OF SCOPE | Direct/external IP hosting (traditional port forwarding) |
| OUT OF SCOPE | The content hosted on the server (bird AI galleries, Warhammer galleries): separate projects |
Three phases, each ending at a go/no-go checkpoint.
Known limits going in, vs. beliefs that turned out to be tested.
| Type | Item |
|---|---|
| Constraint | Hardware capability: old specs capped what the server could realistically handle. |
| Constraint | Budget: no formal budget set; self-imposed ceiling ~$100 NZD, actual spend ~$30. |
| Constraint | Skill set: had many individual skills, but not combined in one prior project. |
| Assumption | Router would have a public-facing IP. Turned out false (CGNAT). |
| Assumption | The project would be too much work / beyond current ability. Turned out false. |
What could go wrong, and how it was actually handled.
The build, as it actually happened.
A second scoping document was written separately, targeting SSH access, file upload, and web hosting as three success criteria. It was drafted before the CGNAT issue was discovered, so it's a useful comparison: what was planned vs. what actually happened.
| Criterion | Planned | Actual |
|---|---|---|
| 1. SSH from outside LAN | Via router port forwarding | NOT MET Blocked by CGNAT, same wall hit with the website. SSH currently only reachable from inside the home network. |
| 2. File upload from LAN | SFTP over SSH, or Samba share | PARTIALLY MET WinSCP has been used throughout via SFTP over SSH, satisfying the method. No dedicated folder/permissions were deliberately configured for it though, so it wasn't a planned deliverable at the time. |
| 3. Web hosting software installed | Install, test on LAN only | EXCEEDED Nginx installed and live publicly via Cloudflare Tunnel + domain, beyond the original LAN-only scope. |
Worth logging honestly: criterion 1 remains an open item, tied to the same CGNAT constraint already on this page, and is planned to be addressed as part of the future full security hardening session rather than solved piecemeal now.
What I'd tell myself before starting this again.
IP addressing is more complicated than first understood.
There's always a workaround if you stay creative.
Security setup is never wasted effort.