• 0 Posts
  • 10 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle


  • 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

  • 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.



  • 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.




  • 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).