Monday, 15 August, 2022
Song of the Day: Mama I’m Coming Home - Ozzy Osbourne
Today, I started solidifying plans for getting my homelab up to speed once I return to school. While at JSC this summer, I was exposed to their server setup, and want to try and emulate a version of it myself. I want to completely change the way I write, run, and store code, moving almost everything from my multiple devices onto one centralized server.
To make full use of this, I will be setting up my own VPN into the network that my server runs on, allowing myself to connect to my server from anywhere. As I learned this summer, VSCode allows users to run codeservers over SSH connections, which I will be setting up.
Aside from that, the other utilities I have planned include:
- PiHole - I want to put a PiHole on the network, using it as a DNS to block unwanted adds. I’ll also add DNS entries for all of my sites/services so that I can access them locally without sending unnecessary traffic out of the network.
- Plex Server - I’m going to be pulling the components of an older computer out of its case and rack mount them. I’ll install TrueNAS Core onto it and add some new hard drives. At the moment, I’m looking at having the weaker NAS host a samba share, which my R620 will use to host a Plex server.
- Vaultwarden - A self-hosted password storage service.
- NextCloud - Similar to Plex setup, data stored on NAS, served up by the R620.
- Apple Dev Server - Hosted on the Mac Mini I snagged, a place for me to test my software on Mac OS.
- Grafana Dashboards - Displaying assorted data for the homelab.
- My website - Hosting my website.
- “Virtual Desktop” - A large linux machine serving the codeserver also doubles as my main linux machine that I can remote into.
Those are my plans at the moment. We’ll see how they hold up when I try to put them into practice.
< Prev Next >