I have hosted a wordpress site on my unraid box before, but ended up moving it to a VPS instead. I ended up moving it primarily because a VPS is just going to have more uptime since I end up tinkering around with my homelab too often. So, any service that I expect other people to use, I often end up moving it to a VPS (mostly wikis for different things). The one exception to that is anything related to media delivery (plex, jellyfin, *arr stack), because I don’t want to make that as publicly accessible and it needs close integration with the storage array in unraid.

There is a lot of collaboration between the different instance admins in this regard. The lemmy.world admins have a matrix room that is chock full of other instance admins where they share bots that they find to help do things like find similar posters and set up filters to block things like spammy urls. The nice thing about it all is that I am not an admin, but because it is a public room, anybody can sit in there and see the discussion in real time. Compare that to corporate social media like reddit or facebook where there is zero transparency.

This is what I do. I have a VPS that handles all the 443 traffic and then proxies it back to my home server on the correct port. I also just serve some things directly from the VPS since I have it already. It also works well to have a second box for things like uptime monitoring.

Some good answers in here already. It boils down to a couple points for me:

• Back when I started selfhosting, it was either nginx or apache, and I found nginx better and easier to set up
• All the nginx knowledge I learned years ago still works just the same as it did back then, so why potentially mess things up by switching if it all still works
• Basically every project has an example nginx config for reference, that can’t be said about other proxies
• It is easier to find support online for edge cases that might pop up with nginx due to the ubiquity of its use and years of history

Intel confirmed on reddit that oxidation did impact some chips.

More than one thing can be wrong at the same time, so everybody can be right!

I didn’t have a VPS with them, but long ago I had a couple domains through them. One of them had an issue with the auto-renewal and I never got a notification of any kind, only finding out when they had taken ownership of the domain, advertising it for sale. Then they wanted some way, way higher amount of money for me to buy it back. So, I don’t have any domains with them any more.

This was years and years ago though, so they might be better now.

Everybody’s pager went off in celebration!

I use Sonarr, but it does mess up sometimes for shows even when you mark it as an anime to use absolute numbering. It most often happens with older shows that have lots of OVAs that are sometimes listed as episodes and sometimes listed as specials, depending on the database. So, if you are having Sonarr manage your downloads, then it can grab the wrong episode if its database (I think TVDB) and the release (usually using MAL numbering) disagree.

I don’t have a solution for you, but I will be watching this thread. Currently, I use Sonarr for library organization, but it doesn’t always work well with anime due to title differences and differences between how seasons/specials are numbered in different databases. So, Shoko was on my radar to try out at some point since it uses anidb.

I used to have my docker updates done automatically. However, as the services I used to run just for myself have started to be used by other people (family, friends), I am less tolerant of having things break. So, instead of something like watchtower, I run diun these days. I have it set up to ping me in a discord channel when a docker update is available. Then, I can actually perform the update when I have time and attention to troubleshoot any issues that may come up.

My house has a similar issue with a lower level that is perpetually much colder than the upper level. The main way we have somewhat alleviated the problem is by opening/closing registers. In the summer, we close all the registers in the lower level, forcing all the cold air from the HVAC into the upper level, then letting it sink down naturally. Our lower level is still cooler, but it isn’t as stark a difference. Due to the layout of the stairs linking the two levels, a fan is not terribly effective at exchanging a lot of air between the two on its own.

As for whether he forgives Morrissey, Carroll said: “I guess I would have to say yes in the spirit of forgiveness, reluctantly. But if I had to be a smartass, I’d say her apology holds about as much water as my canvas bag.”

Fantastic.

This lines up with my experience. I have nextcloud and wordpress on two different vps’s and just checked their ram usage.

• nextcloud: 468 MB
• wordpress: 120 MB

Caveat to the above is that nextcloud is installed bare metal rather than docker and I have both nextcloud and wordpress set up to use object storage as the media back end.

edit: To add to this OP, the reason we are only talking about ram numbers is that the cpu usage for these applications (with primarily only a single user) is pretty much zero most of the time, so you aren’t going to be limited by the single core machine.

Also, depending on your use case (large amount of data on nextcloud or large media files in wordpress), you might run out of disk space pretty quickly. In those cases, you should consider using object storage as your nextcloud or wordpress media backends as it is cheaper than block storage (there are plugins/tutorials to configure object storage and Linode offers it).

My isp doesn’t support ipv6 in my area (Verizon). They claim to be in the process of rolling it out, but it’s been years that they have been saying that, so idk. At least they don’t use CGNAT, so it isn’t a huge deal for me after I set up dynamic DNS.