this post was submitted on 04 Jun 2024
883 points (98.7% liked)
Technology
60085 readers
4929 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
because it was super duper easy to setup and the overhead isn't all that bad for my use case. I am concerned whenever I decide to move/upgrade to something different since my hard drives are in a Windows "Storage pool" or whatever it's called
In all seriousness, if you're self hosting anything, please learn your way around Docker and Linux. It's a small time investment up front for huge payoffs. You'll get more value out of your hardware, and you'll have a system that's much more reliable (Windows was not built for 24/7 uptime).
In fairness, I've had several machines running versions of windows server with lots of uptime and zero stability issues. But the last time I ran a windows server is was advanced server 2003 so....
Windows Server isn't so bad as a server platform, although it comes with a lot of unnecessary overhead, and its container support sucks. Given that containers are really the way to go with self-hosted services now, that makes Windows Server a poor choice.
But realistically, when most people say they're self hosting on Windows, they mean regular old consumer Windows, which absolutely hates running for extended periods without rebooting. It's just not built for uptime.