Good to know. Thank you!
Good to know. Thank you!
I ran into an issue where I changed nothing, and all of a sudden none of my SSL certs worked on top of most of the hosts were not working through the reverse proxy. I had not even changed ip addresses on any of them. I am not sure what was going on.
It was more of a “I didn’t want to troubleshoot” and gave up, so I shut down my servers.
Today I learned about Linkwarden, and I am so excited to check it out. Thank you!
NPM I did use, however it was ultimately the catalyst as to why I quit homelabbing. But when it did work, it was simple even for SSL cert renewal.
I will have to check out gitolite. Thank you!
Traefik or Caddy are the 2 I am bouncing back and forth between currently. I may spin up a nextcloud instance.
I still want to get familiarized with NixOS and the concepts behind it. Just haven’t taken the time.
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.
Saying you don’t care about privacy because you have nothing to hide is like saying you don’t care about freedom of speech because you don’t have anything to say.
I actually suggest getting Ventoy which is a fantastic utility that allows you to copy bootable images to a folder, and when you boot the drive you can select from the ISO/Images available on the drive. Super handy!
The Live USB may not solve all HW issues, but it’s a good jumping off point.
I can’t blame anyone not going the pure arch route, and choosing an Arch based distro. Besides getting my GPU working as I wanted it, running and maintaining my Arch install is no work at all at this point. With Timeshift installed, as well as the grub hook, and pacman hook, it makes it a cake to revert if something breaks.
The other advice I have for Linux is an often overlooked. When switching to Linux you can’t always approach fixing a problem or operating the machine the exact same ways one would on Windows. So being flexible, and learning to change habits helps.
Besides the usual back up your files advice, I have a few recommendations.
These recommendations are not in any particular order but:
Consider all of the applications you use on Windows, and research alternatives for those applications. Or if there isn’t a replacement for it, investigate how to get the application you need working in Linux. For instance, I use a lot of audio production software and learned that there are a few that just do not work reliably or at all within Linux.
Depending on your needs be sure to research (or better yet, try) different Desktop Environments. (Note: for trying different environments I would recommend finding a distro that has a Live USB option and run those live to test them out)
As I mentioned in the above suggestion, try different distros you are considering using with a Live USB. This can help snuff out different hardware that you have that may or may not work on your system before committing.
Before choosing which OS you want to go with, consider the key beliefs of how to maintain an OS. For instance, there are many people that will blindly recommend a distro without knowing why one would use it. There are bleeding edge rolling release type distros such as Arch. I use Arch BTW, but I would not blindly tell someone who just wants a stable experience with little to no tinkering needed.
Most of my suggestions come down to please do your research, and make an educated decision on what you want to jump into. And I like to think that there are plenty of communities that can be friendly and welcoming that would help!
I bought a 2024 vehicle with OnStar, I wonder if the process is comparable… Could you share your source please?