I’m a Windows guy since forever and I recently got into selfhosting. So far its a blast! Are posts about that welcome here?

Sure, but know you’re doing things the hard way. I started with Win 10, WSL, and Docker Desktop but moving to Linux made things 10x easier, Windows is… difficult.
Are posts about that welcome here?
Absolutely. The gate’s open…come on in. It’s been quite a while since I’ve had a Windows based server. I still run Windows 10 in the lab, plus Linux and Mac. I don’t really discriminate. All OS’s have their place imho.
So far its a blast!
That is one of the prime directives of selfhosting. I have a ton of fun learning about new stuff to do and how to do it. Tell us all about it man. What do you selfhost? Are you running any Docker containers? I’m all ears, which in reality isn’t too far from the truth with my Jumbo ears. Share! Share!
100% there is room for Windows self hosters. Welcome. May your self hosting be productive, secure and fun.
I would recommend at most ruining windows as the hypervisor then running Linux virtual machines. Maybe run a windows VM if you have a specific need.
This is mainly because Linux is much better “supported” for the majority of self hosted projects.
But you can of course do whatever you want.
I also recommend ruining windows
I self host on windows. It just happened to be what I had on the box. Then I got started with docker. So that was great. When I have the time, I hope to switch to unraid, but need the time to be open enough to deal with the problem that will arise in getting the system set up just right.
Are you hosting on win server? I’m genuinely curious, not trying to shill Linux though I prefer it on the server side, believe me I’ve been on the receiving end of that for desktop Linux. How do you manage it? Do you have your home LAN set up as an active directory domain? Do you use mostly Powershell or the GUI? What do you have running on it? It just seems like everything on the server side assumes you’re using Linux and the only stuff that runs on Win server is stuff made by Microsoft like MS SQL server or IIS.
You can find a description of my first project here https://lemmy.world/post/48204688
Private email. Very nice 👍
Thanks!
One step at a time, you will eventually move to GNU/Linux in the future if this new hobby persist. But there is nothing wrong with beginning using software and tools you are already familiar with. However you will probably have to use WSL (Linux inside Windows basically) to make things work and all guides you will find will mostly be based on Docker and/or Linux. So you will definitely use Linux on your Microslop owned machine.
If you don’t have the time to learn a new OS it’s fine, but it will not necessarly make things easier, especially on the long run. That’s my take on it.
My very first self-hosting homelab was a Linux Mint old refurbished desktop PC that I was remotely accessing through AnyDesk (I was a Windows kid user at that time). Now I’m on NixOS through SSH and still learning, I do not completely comfortable but I am able to use it and learn while doing so.
I would highly encourage you to try to run a lightweight beginer friendly Linux distro such as debian, Linux Mint XFCE or Kubuntu if you feel like you need a desktop environement and graphic user interfaces but if you really want to use that Microslop license you bought it’s fine, you will probably switch in the following months or years. Okay maybe not, some people are fine using it.
You can also take a look at stuff like runtipi, yunohost, CasaOS, ZimaOS, Umbrel, Cloudron and stuff like that. They aim to be beginner friendly self-hosting “OS” or “WebUI”.
Linux is favored because the ecosystem is more open but you can also run it on low power devices which isn’t really the case with Windows (and getting worse over time) and it’s free with Windows, to be legal, you need to license the cores/VM. Now does anyone actually do that?! I wouldn’t think so.
I started out self hosting with windows server 2012 because my school was a Microsoft and Cisco partner but mostly ran Linux VMs on it using hardware raid. Ran bitwarden, Plex and a wiki plus a VM with a bunch of docker containers. Ran that for about 3 years and now have been on Unraid for 6 or so years and loving it.
Windows hacking is just as fun as anything else, sometimes it’s even more rewarding just because you made it work on windows! My favorite is replacing the windows shell… Haven’t done that since 7 though :(
I’m not a windows hater per se, but I am for using the best tool for the job.
And in my opinion windows is not the best tool for self hosting. There are things windows does work well for that meshes well with self hosting and that’s docker. Honestly I’d focus on that for a lot of reasons but primarily because it’s a very easy to deploy self contained way to provide services. And the differences between docker on windows and Linux is almost negligible.
I self hosted windows for many years, mostly because that is what I used at work. I liked it because it hid some of the low level details and worked most of the time.
The thing that finally made me switch was the exorbitant cost of licenses and the need to run services on older hardware.
DM me if you want some keys. I have a few copies of win10 and winIOT laying around that I’m not going to use.
Sure thing!
(also, please do post about it when you eventually decide to switch to linux)
Many of us started running Windows Server and endpoints, but in my case, the cost and substandard tools turned me away. I was running A DLNA server and using WDS (yes, very overkill for home, but fun to learn for work), but then I found TrueNAS (then called FreeNAS) running on BSD. I now run a simple share from there and Kodi on my (Linux and Android) user endpoints. I don’t bother with imaging anymore, and use
ddfor backups to my NAS. My Firewall runs OPNSense (BSD) and I run OpenWRT on two TrendNet WAPs.I’ll never go back to MS. It’s just not a welcoming platform from my perspective. Don’t even get me started on .NET or the various and sundry “redistributables” constantly required by every tool you try to use.
Don’t even get me started on .NET or the various and sundry “redistributables” constantly required by every tool you try to use.
It’s absurd but Linux is far worse. Instead of addressing library bloat and versioning we have Docker which just throws EVERYTHING into a bag and makes you download an entire OS environment space to run one app.
And that is perfect. Instead of setting up one VM for each service and manually updating all dependencies, I’d much rather use that very handy bag with everything in it.
But the op is complaining about the much lighter .net where the shared libraries for all apps are a fraction of the space of bringing in an entire OS environment for each and every app.
That’s not Linux, though; that’s docker.
.net isn’t Windows.
dotnet is pretty great, runs great on Linux, and you can ship your executable without a need for an external framework if you want.
Dotnet is also open source, a strongly typed language, a large standard library so it doesn’t have the problems of npm, has great performance and is all around the best language out there imo.
Use rust if you need to be closer to the metal, but that’s rare.
Maybe now. .NET wasn’t always open, used to be Windows-only, was buggy, version-dependent (but not as bad as the jre could be; true), and had (still has) poor resource-management. I think you’re talking about .NETCore.
That said, I wasn’t commenting on the code viability (I’m not a professional developer) so much as the support overhead required (back when I worked support) for the different versions of .NET, especially when MS stopped including v3.5 in Windows except by using “features and programs” or downloading and installing it manually.
Yeah, that’s pretty dated. There’s one flavor of dotnet (more or less) that runs on everything, and it’s about as efficient as anything with a garbage collector can be.
There are hairs that could be split in there, such as the release cadence, hosting bundle vs desktop runtime, but that’s all much simpler than it used to be. You generally know if you want to run a desktop app vs a webserver.






