Trying to setup Nextcloud calling on docker 🥹

1st: Virtualization

2nd: Firewalls and networking

3rd: Containers, Docker, (Podman) and LXC, (Incus)

4th: All the above leads onto Hypervisors

5th: Which leads you to Kubernetes

The first three require minimal hardware. Once you’ve got the hang of the them, it’s time to get serious with a dedicated machine with greater hardware resources to run a Hypervisor.

Kubernetes, all that built in redundancy makes it hungry beast. Enough to get you looking for one or more those big old servers that homelabers love.

V

VMware vSAN cluster, ceph cluster, building HA for different services, containers, k8s cluster. The list goes on.

Setting up a small website hosted locally helped me understand the whole stack so much better. Roles / permissions / firewall rules / ports/ webservers / appservers / devops / daemons / docker / DNS and a bunch more

set up dedicated game servers to share with friends. Especially on some hyperviso.

my video game bot farm gave me desire and the need to learn… 1.programming. 2.database administration, 100s of bots need a database. 3.advanced home server deployments and virtualization, 100s of bots need hardware. 4. logging, you cant observe 100s of bots you need to log their activity and establish and observe metrics. etc… I could keep going but after this I started my career as a mainframe programmer, because I had like 70ish percent of the skills I needed.

Running my own vmware server

Configuring guest network

Multiple vlans

Configuring tagging on switches for said vlans

Installing Linux on a VM and taking the plunge to learn it.

Truenas/Linux Proxmox/Virtualization Docker/Containerization/Portainer Traefik/Reverse Proxy/SSL Certificates PiHole/DNS

I’m going into my 2nd year self-hosting and home-labbing. i learned all of these skills from watching TechnoTim, DBTech, Network Chuck, Raid Owl, Christian Lempa, Level1Techs, Learn Linux TV, Awesome Open Source, Craft Computing, and Jeff Gerling. These guys are awesome i highly recommend them.

Oh…wow. That’s quite the loaded question. How much time do we have? ::checks watch::

The short answer is that almost every technical skill I’ve learned or improved (and some non-technical ones like public speaking as well) has been a result of my home lab. I just needed the right push/motivation/use case to dive into it.

The first iteration of my home lab started 20 years ago while I was in college. I started my lab because I wanted more hands on experience, and my curiosity pushed me forward from there.

So…it really depends on what skills you want to develop and where you want to start your career. IT is a very large area.

The best thing you can do is find problems you have and use your lab to design and implement a solution.

In general, I would say the following:

1. Troubleshooting- Build things in your lab just to break them. Learn how to figure out what you broke and how to solve the problem.
2. Networking - Build a network. Understand how applications and services talk to each other. Learn a little about TCP/IP and basic routing. It doesn’t need to be complex (unless you want to go for your CCIE)
3. Virtualization - Build out a small virtual environment. Use it to run a few applications or services for personal use. This is also good because you can put multiple services on the same piece of hardware.
4. Share what you’re doing - A big part of IT is communications skills. Once you start doing something interesting, share it. Blog. Find user groups for the technology you’re interested in and talk about how you use your lab to learn it. Good communication skills will get you further than good technical skills.

A robust PKI implementation.

Setting up a full k8s cluster (vanilla k8s, not k3s etc.) and running most of my self-hosted apps in that cluster caused me a lot of headaches but also got me an immense amount of knowledge and experience.

Setting up exchange server cluster with backups, OWA webmail behind reverse proxy doing IPS+SSO+ MFA, setting up DKIM, DMARC and SPF for this server / testdomain.

Windows PKI using offline and issuing CA. Using these certificates for 802.1x auth.

Hardening Windows Active Directory, setting up LAPS, enforcing TLS where possible, restricting service accounts etc.

Using Azure AD for SAML SSO to where possible. Using JIT or SCIM prorvisioning for accounts. Access roles from groups etc.

Setting up Intune managed workstations with device complience policies and using these policies in conditional access policies.

So yeah mostly Windows stuff.

setting up a pfSense router is cool.

you can use docker to run some local services and give them their own domain names with pfsense

if you want to progress further, you can use traefik to give docker/kubernetes services hostnames and get a cloudflare certificate to enable https on everything

Im a little “seasoned” at 45 rotations around the blue ball so YRMV lol

1 - Pirated Movies - XBMC -> Plex (2 bare metal servers with transition to Virtual in progress)

2 - Storage - Freenas -> Synology (300+TB across 6 units)

3 - Networking - Unmanaged -> Managed / Multi Vendor / LACP / WIFI

4 - Compute - ION Based NUC -> ThinCentre / ML360G6

5 - Virtual Envio - Single ESXI Host -> 5 Node Proxmox Cluster with Ceph on 10G

Basically for me it started with Saving private ryan on VCD / CDR back in the day, that led me down the IRC rabbit hole and i got into XBMC for playback. That meant NAS storage for more movies and then from XBMC i moved into Plex so needed more server based compute and such. All the while needed to learn networking to hook it all up and make it work correctly.

I also went from working at Terminix as a pest control operator to doing customer support via email for a .com in the early 2000’s to now leading technical deployments at a forture 10 pharma :)

All cause of Saving Private Ryan on Pirated VCD in CAMMED quality lol