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.

even after renaming MangoHud.conf to MangoHud.conf.old in ~/.config/MangoHud/ And launch a game with MangoHud, it does work. However, where would the config be if it doesn’t show up in ~/.config/MangoHud/

That’s what I am trying to figure out, the Readme and Archwiki don’t have the paths I am looking for.

AI isn’t a magic bullet. Sure it has it’s uses, but you have to weigh it’s usefulness to the ideology behind a project and it’s creators. Just because a software developer or community doesn’t embrace AI doesn’t mean they will be “obsolete.”

AI is the current trend that is being shoehorned into everything. I mean literally everything. I don’t think we need AI touching everything.

I don’t want or need AI crammed into my desktop environment. And I surely don’t want it interjecting into my filesystem with my data. It is a privacy concern. And many of other people will feel the same or similarly as I do.

AI is a tool, and with all tools: use the appropriate tool for the job.

While I can see the merit of your sentiment here, and would generally agree the world exists on a spectrum and not some binary scale of yes or no, black or white. Like others have said, with mottos like “Embrace, Extend, Extinguish” how can one ignore the bad that Microsoft brings to the table.

Microsoft just like many other big tech companies are shoehorning AI into everything. It’s a new fad, and if it isn’t a fad, this is how idiocracy starts IRL.

Oh no judgment, purely curiosity here.

I have used both, but have stuck with nano. Why do you personally choose micro over nano?