I may have to check out BookStack. I dig the looks of it.

I appreciate that mentality though. When things break, if your understanding of your setup is there, it’s less to deal with.

I am forgoing the Portainer route this time. I am going to strictly use Docker Compose for my containers. I had too many issues with Portainer to consider using it.

For reverse proxy, I just need/want it for simple ip:port to sub.domain.lan type addresses locally. Anything I need outside of my home will be tunneled through wireguard.

I always quite liked Dozzle. It was handy, and has helped me comb through logs in the past.

I think Traefik is going to be what I investigate using. However the last time I tried, I was a little lost. I will have to comb over the documentation better this time.

That is good advice, and honestly never really occurred to me to set specific versions for containers.

I will likely dabble with Logseq.

I used NGINX Proxy Manager for a while, then had some issues that ultimately killed my homelab setup, so not sure that I want to go down that route again, or if I want to investigate Caddy, Traefik, or another.

I think I am going down the docker compose route. When I started using docker, I didn’t use compose, however, now I plan to. Though, Ansible has been on my list of things to learn, as well as nixOS.

Thank you for the suggestion. The fact that it’s FOSS wins my vote. I have been trying to go all open source where possible.

I think I need to utilize this strategy because I get lazy and don’t update external documentation.

I really should spend time familiarizing with maintaining a git repo. I’ll likely find one I can self host.

I have looked at Obsidian, it looks nice, but the closed source part is why I can’t personally use it. Though, from discussions I have seen Logseq be thrown out when talking about similar software.

The wiki idea is a good one. The way to handle that is to have the wiki backed up incrementally.

This interests me. I may have to check this one out specifically for my configuration files. And I will definitely go the self hosting route if I do this. Thank you!

I can see two sides to this:

Removable batteries are great, if you want longevity for a phone, and don’t mind sacrificing water resistance.

On the other side of the coin:

Removable batteries have more potential to lower water resistance ratings.

I think more manufacturers should give the choice of a model with a removable battery.

“Verizon agrees that the FCC should consider the merits and trade-offs of handset unlocking requirements,” Verizon spokesperson Rich Young told The Register, though that support is conditional.

Screw verizon with an acid covered cactus. What possible “merits” are there to locking a device down for anyone but the companies selling the phones? Rich Young can go kick rocks.

I will not buy a phone through a carrier, I will not buy a phone with a locked bootloader. Period.

I am done with anticonsumer bullshit.

You should go another level deeper, VirtualBox > Windows > WSL > Waydroid > Lindroid

Back on windows I have used Resilio Sync. I don’t hate it, does essentially what I am looking for, but I am trying to go more open source route. Thank you for the suggestion!

Fantastic suggestions. Gives me some things to try. Thank you so much!

I have seen the likes of similar, like Andronix but I typically don’t want to buy into proprietary software where possible. Thank you for sharing!

All good!

I will have to give this a look! Thank you!

That is fair. Just historically speaking, I have typically only had 1 port opened on my router for VPN access, and then setting up SSH cert auth from system to system.

Like Shrek, layers xD