Grafana Dashboard
At the very start of 2026 I was wondering what I could implement to my home server that would showcase my fluency with enterprise-level server adminstration. After doing some research (applying for jobs online), I found that grafana popped up a lot. I decided that I would set up a grafana container on my home server. I was intially confused but I now the grafana itself is only the visualization for the data scraped by prometheus, which I also incorporated into my docker-compose.yml, below is the live monitoring of my home server's current RAM usage, along with some other stats:
Minecraft Server
Who doesn't love minecraft? My friends in the rowing club as well as the binghamton crosbys both love playing minecraft.
however, despite my efforts they don't seem like playing minecraft across their respective friend groups.
my task was to create a way for friends in both groups to play minecraft in their seperate worlds. to do this, I first had to spin up a second instance of my minecraft docker container.
It only got harder from there: I messed around with my DNS records and added a second SRC record, which allowed me to assign a new port for the new server directly to a subdomain, meaning neither party had to enter a port number when trying to log on. simply reaching <server one>.seniho.com, or <server two>.seniho.com would connect you to the respective instance of the minecraft server. After a particularly harrowing greifing event on one of the server, I integrated a basic whitelist protection that registered users to the server by having them visit <server 1/2>.seniho.com/whitelist, and submit their username. this was tied to a node instance on the backend that connected to the respective server instance in the docker container and added the username to the whitelist. obviously this isn't best practice, but it prevents scrapers from finding an exposed minecraft server through the standard port.
