Oh no, you!
This mostly comes down to your preferences, but my rule of thumb is that everything should be on mgmt vlan for mgmt, and then you choose which of those to expose to other VLANs via secondary interfaces. This has the benefit of allowing configuration when you’re on the management vlan only, and limiting access to the service itself.
Hetzner is pretty cheap, and have datacenters all over (I mainly use the one in finland). For your usecase, a very cheap VPS shoyld do. If you want a physical machine I can recommend their server auction.
Used it in the past, and it’sa pretty alright desktop OS. It would work as a server OS, but that’s not really its main focus.
It’s debian based, so might as well go for actual debian.
It’s been a while since I selfhosted my email, but I found it pretty efficient to set up a spam filter that periodically logged into my Gmail address and used its spam folder to train a bayes classifier.
Been a hetzner customer for around 20 years. No regrets.
It said 1~2 originally
Still more plausible than 1W
Yeah, it sounds more plausible like it’s amperes
I heard it’s a Mastodon thing
ssh
Barebones, usually. In general I prefer software that does only one thing and one thing well. Input or output to/from said software can be handled by other pieces software.
I’m a big fan of modular designs where you can swap out any layer with something else, provided that the data interchange is c9mpatible.
Lacking the above, I usually go for softwares with support for plugins/extensions.
Same. Got some leftover Fortinet from work that I’m using. Could be better, but my Fortigate 101E works miles better than my ISP default router. All I had to do was assign upstream wan to VLAN 10 and spoof the MAC address.
I don’t have experience with hosting lemmy specifically, but from what I hear it doesn’t require much other than being a bit RAM-hungry. Add some swap space, use the instance primarily for yourself, and you should be good.
Hosting does not attract CSAM on its own. Anonymous uploads do. Only host services that you find useful yourself, and maybe sharing it with friends, and that’s a reasonably safe start.
Does sshd count?
Beyond the “default” stuff, I always seem to end up with a setup that involves linux + apache + mod_perl + postgresql for various purposes. And by the way, that’s the only proper LAMP stack in my book, and I will die on this hill.
Normally it doesn’t matter. The only restrictions is in terms of who can buy domains of that country to begin with (some countries have restrictions on that), and what sort of content is allowed in such domains. Other than that, it’s OK.
I’d say that a good starting point would be the smallest setup that would serve a useful purpose. This is usually some sort of network storage, and it sounds this might be a good starting point for you as well. And then you can add on and refine your setup however you see fit, provided your hardware is up to it.
Speaking of hardware, while it’s certainly possible to go all out with a rack-mounted purpose built 19" 4U server full of disks, the truth is that “any” machine will do. Servers generally don’t require much (depending on use case, of course), and you can get away with a 2nd hand regular desktop machine. The only caveat here is that for your (percieved) use cases, you might want the ability to add a bunch of disks, so for now, just go for a simple setup with as many disk as you see fit, and then you can expand with a JBOD cabinet later.
Tying this storage together depends on your tastes, but it generally comes down to to schools of thought, both of which are valid:
Source: Hardware RAID at work, software RAID at home.
Now that we’ve got storage addressed, let’s look at specific services. The most basic use case is something like an NFS/SMB share that you can mount remotely. This allows you to archive a lot of the stuff you don’t need live. Just keep in mind, an archive is not a backup!
And just to be clear: An archive is mainly a manner of offloading chunks of data you don’t need accessible 100% of the time. For example older/completed projects, etc. An archive is well suited for storing on a large NAS, as you’ll still have access to it if needed, but it’s not something you need to spend disk space on on your daily driver. But an archive is not a backup, I cannot state this enough!
So, backups… well, this depends on how valuable your data is. A rule of thumb in a perfect world involves three copies: One online, one offline, and one offsite. This should keep your data safe in any reasonable contingency scenarious. Which of these you implement, and how, is entirely up to you. It all comes down to a cost/benefit equation. Sometimes keeping the rule of thumb active is simply not viable, if you have data in the petabytes. Ask me how I know.
But, to circle back on your immediate need, it sounds like you can start with something simple. Your storage requirement is pretty small, and adding some sort of hosting on top of that is pretty trivial. So I’d say that, as a starting point, any PC will do - just add a couple of harddrives to make sure you have enough for the forseeable future.
Back in the day I used Nagios to get an overview of large systems, and it made it very obvious if something wasn’t working and where. But that was 20 years ago, I’m sure there are more modern approaches.
Come to think of it, at work we have grafana running, but I’m not sure exactly what scope it’s operating under.
Barring any hardware issues or external factors, will it run for 10000 years? Any logs not properly rotated? And other outputs accumulating and eventually filling up a filesystem?
Depends if you’re hosting something public, or something private.
For public, a webserver is a simple start. Can be anything you want it to be, but as complexity increases, so does the amount of potential attack vectors, so keep that in mind of you’re considering adding things like WordPress and the like.
For private, a NAS and/or a simple game server is a simple and useful start.
As for how, there’s a million ways to do it, and I’m an old stubborn BOFH that still cling to the old ways of doing it (as in, no VMs, no containers), so I’ll defer to others for that.
While purpose built server hardware is always nice since it comes with some useful additions, the truth is that “any” machine will do. Old discarded PC will do just fine.