Yay finally got #ZFS running in a mirror #raid configuration. +1 for data redudancy and hopefully zero data corruption.

I'm late to the party, but might as well see if I can put some energy into the #100daysofhomelab tag.

Im trying to be generous and just give myself credit for most flavors of productive computering.

Obligatory Day 1 post https://blog.lane-fu.com/posts/2025/03/100-days-of-homelab-delayed-start--day-1/

Day 8 of #100DaysOfHomelab : Sorted out #backups for a few services, restarted #qbittorrent via #docker this time. I tried to auto boot my #LUKS drive via #TPM2 key have to figure it out now.

I have a small #HomeLab which provides #Pihole, recursive #DNS via #unbound, #jellyfin, #nextcloud and ofcourse #backups for a variety of services which I host or manage.

I started #100DaysOfHomeLab on Jan 10 to get rid of all the #techdebt - streamlining scripts, ensuring backups, full disk encryption, getting more services running.

So far I have bought another 2TD HDD and trying to put my current setup into mirror #raid using #ZFS.

[013/100] #100DaysofHomeLab

Today I managed to get #immich up and running. Boy, is this ever an obvious UI clone of the product that shall not be named, but im here for it! I am thankful to have some ownership of my photos again.

Now about that NAS that I *dont* need....

[012/100] #100DaysofHomeLab

I spent a long time trying to get #Docker logs in #Grafana Loki today using the native connector. Nothing seems to be working quite right.

I want to love the Grafana stack, but it seems to be at odds with me at every turn. Does anyone have suggestions for #selfhosted full observability platforms? I'd ideally want metrics, logs, and traces with alerting/notifications as a nice to have.

I may go back to Signoz if I can't get this logging to work.

[011/100] #100DaysofHomeLab

Today I learned a little bit about #NGINX location routing. I wanted to deploy an application under a root location but not pass the root location along to the downstream app.

Ex: `http://example.com/apps/app1/home` ==> `http://10.0.0.1:80/home`

Turns out I needed a combination of things:
`location /apps/app1/ { proxy_pass http://10.0.0.1:80/}`
and
`location ^~ / { proxy_pass http://10.0.0.1:80}`

This link helped:

https://serverfault.com/a/562850

[1/2]

[010/100] #100DaysofHomeLab

Tonight was a simple hardware upgrade. Now my two main #Proxmox nodes are running matching hardware: i7-6700T (4c/8t) with 16GB DDR4.

The little Optiplex "micro" PCs from Dell really are the sweet spot for Homelabs. Small, (relatively) power efficient, easy to work on (upgrade took 15 minutes tonight including a reboot), and pretty cheap these days (especially when you consider the price of Raspberry Pis now).

[009/100] #100DaysofHomeLab

I feel like this should have been obvious, but since I'm already using #Ansible to configure my infrastructure applications, why not also use it to deploy my "fun" applications as well on each new commit.

Found this article that will guide my initial configuration.

https://spacelift.io/blog/github-actions-ansible

[007/100] #100DaysofHomeLab

Spent some time today thinking about how I want to do dev / stage deploys of containerized applications on the lab. No solid conclusions yet.

[008/100]

Came across the `-H` flag of docker-compose. This seems compelling. But, now I need to figure out how I want to dish out and store SSH keys to my runner. I'll probably do some sort of #Ansible solution with Gitea secure variables but I'm leaving the door open.

[006/100] #100DaysofHomeLab

Today, I was able to get my #Gitea runner working and publishing containers to my self-hosted registry ... only to realize that Gitea has a built-in container registry that I could have used instead.

Does anyone have a good reason for running a #selfhosted independent registry outside of learning or the need for ultimate control?

[005/100] #100DaysofHomeLab

Spent most of yesterday trying to troubleshoot why my #Gitea runner isn't working. I'm getting `getaddrinfo ENOTFOUND server` when on the `actions/checkout@v4` step.

It seems like there might be some connectivity issues between the runner and the server even though they are defined in the same docker-compose stack and #docker network.

Hopefully today I can make some progress on this and get a full Gitea deployment working.

[004/100] #100DaysofHomeLab

I didn't have much time for deep work today so I decided to update some network/service diagrams. It's still not perfect but at least it's written down.

[002/100] #100DaysofHomeLab

Upgraded one #Proxmox node from 7.4 to 8.2. One left to go but that's PROD so I'm taking things slowly.

I also tried to install a global Gitea runner. But, after it succeeded I thought all of my #DNS broke (NS_Unknown errors). After re-running my #Ansible scripts with no success, I finally realized I'd moved rooms and disconnected from my wireless network that's isolated for homelab work.

The `dig <domain.name>` command was what tipped me off.

I'm way late to the party but I think I'm going to try #100DaysOfHomelab. I've been doing it sporadically but with increasing consistency so why not make it a habit?

[1/100] Today I installed #Gitea on a test VM. So far, it seems much less resource intensive than GitLab. All I really need is some version control and action runners so I think I'm going to like it a lot!

Is the terminal still worth learning?

https://tinkerbetter.tube/videos/watch/63bb7e54-e4bf-4428-9cdc-6f8941546789

I did #100DaysOfHomeLab for a year, here's what I learned

https://docs.technotim.live/posts/100-days-of-homelab-1-year-later/

Day 359 #100daysofhomelab

Upudating MySQL Server!

Is the terminal still worth learning?

https://tilvids.com/videos/watch/bc382aab-55c7-4733-98b8-3e5e5234f8d9