https://arstechnica.com/health/2025/06/new-covid-variant-swiftly-gains-ground-in-us-concern-looms-for-summer-wave/

Unfortunately I seem to have come down with the flu late last week, and it's still hammering me really hard, so all my projects are on hold for the moment as I barely have the energy to type.

Haven't been this sick since I had pneumonia 25 years ago.

naturally there would be some S&H unless you're close enough for a pickup/delivery/meet-in-the-middle-exchange. what is your zip?

All that aside KEEP YOUR SOFTWARE SEPARATE FROM YOUR DATA. Have your OS on a separate drive or raid array than your data. JMHO I would setup timeshift on your OS drive and at least a RAID1 on your data possibly a RAID10 but that might be overkill. And then have some old POS machine in the corner with a RAID1 or just 2 drives doing nightly RSYNC backups from the main server.

What I do at work is I have a spare drive in our server getting RSYNCED 5 days worth of our critical data to the secondary drive, I then have that POS machine in the corner with 2 drives making 2 copies (no need for raid) and that machine RSYNCs nightly up to RSYNC.net

I wonder if it will be a software issue going forward if I used a non-uefi system to start with if the board will support it?

Highly unlikely. The only software that cares about UEFI/MBR distinctions is the bootloader and whatever is installing/updating it, and I don't see GRUB or LILO dropping MBR support any time soon.
If it ever did come to that, converting an installed system to UEFI isn't particularly difficult anyway.

The more likely scenario is that at some point you will need to replace the motherboard, and find you have to pay a premium for one that still supports MBR boot.

What you *need* UEFI for is booting from (almost all) NVME drives, and that is a technical/architectural limitation... So as storage moves in that direction, sooner or later you will have to adapt.

Also worthy of side-note is that resizable BAR (or whatever $GPU_vendor is calling it these days) support in BIOS is currently being used as a wedge to push people toward UEFI. There's no technical reason for one to require the other, but that's what consumer board vendors (and more to the point, Microsoft) are doing.

Why? We're not talking about a home NAS here, and using a turnkey NAS distro adds precious little of value to a webserver.

If you are an idiot and run compromised or misconfigured services, sure. Or you could... *shock* read the Debian security manual.
I know plenty of people (myself included) running public webservers on general-purpose GNU/Linux or BSD distros, none of them have been pwned, and I call FUD.

Devuan is exactly as "suitable for online use" as Debian, and both can do everything TrueNAS does if configured appropriately.
Debian powers vast numbers of webservers and has for decades, whether it has an easy-mode "GUI tool" or "setup wizard" for a given role is neither here nor there. "Universal operating system" and all that.

I'm not knocking TrueNAS mind, it's a fine distro... Claiming that it's somehow more reliable or more secure than Devuan because it has a graphical wizard though, that's kinda ridiculous... As is shelling out $199 per box for HexOS beta, the mind boggles.

Despite having my daily driver PC on AMD hardware for the past 25 yrs, I'd suggest you'd hunt down an older workstation (Intel 10th, 11th or 12th gen CPU) for cheap, maximize RAM, add 2-4 HDD's for long term storage in RAID 1, 5 or 6, a 1TB NVMe SSD for the OS and any VM's you'd like to run.

As for the OS: Although Devuan can do all the tasks you planned for, I'd suggest being practical and consider specific NAS-OS's like HexOS, TrueNAS Scale, UnRAID or ProxMox instead. Yes, they use systemd and as much as I despise it, realistically that's not going away anytime soon. As your only online portal for your community, downtime due to having to tinker with a manual Devuan setup isn't really acceptable. You'd also need to consider online risks: you may not consider your community a target, online criminals will have a field day hacking your machine and turning it to making them money whichever way they want. Devuan simply doesn't have a GUI tool that makes configuring it suitable for online use, like HexOS is for TrueNAS. The project lacks the resources and realistically, it's not gonna happen anytime soon, even if someone steps up developing the required functionality for it today.

I can feel your pain from way down here.  8^°

Food for thought:
From your OP I gather that $$$ is a limitation and a very understandable one.

As you know, I run my Devuan system on a ca. 2007 Sun Microsystems Ultra 24 WS.
Doesn't ever skip a beat and it is the best IT purchase I ever made.
The box is built like a tank, way ahead of its time when it came out and still was 10 years later.
You don't get hardware like this anymore.

Why not consider an older, high quality box to populate with enough RAM, SAS controller / drives and a pair of 4port Gigabit cards?
I think that is where you will get the best bang for your town's money.
And no EFI ...

eg: a Sun Microsystems Ultra 40 M2.

2x AMD 3.0 GHz Opteron dual-core processors + 32 GB of DDR2-667 ECC
2x 10/100/1000BASE-T Gigabit Ethernet ports
8x SATA / SAS HDD slots
2x PCIe x16 graphics slots
2x PCIe x8 expansion slots
1x PCI 33MHz, 32-bit slot

It probably has (like my U24) pins for a RS-232 port, which has to be enabled in BIOS.
Could be quite useful.

You can probably get a basic one for a good price and populate it according to your needs.

eg: run it with no monitor, use 1x PCIe x16 slot for a four port GbE card, 1x PCIe x16 slot an 8 port SAS controller and boot from a SSD drive on an adapter in one of the expansion slots and you will still have 1x PCIe x8 and 1x PCI 33MHz 32-bit slots for whatever else you want to stuff in there.

Just my 0.02 ...

Best,

A.

The list in the OP doesn't have a GPU, the integrated graphics are probably fine. But you did mention media transcoding, and that may be something i'll need to do here and there. It's ridiculously slow to do so on my APU-equipped laptop, would be nice to have something faster.

So the concensus seems to be do RAID1 for the OS too...interesting, not something I would have thought of.

One big question: Is this gonna work without EFI? Because I do hate it so.

I've learned the hard way that SSDs aren't great for long term data storage, especially with static data (files that don't change). Based on what I can figure out from research, the SSDs memory cells suffer from voltage drift over time.

I've learned the hard way that *all* readily available storage media is subject to this kind of bitrot, and the only viable solution (besides exotic media like etched sapphire) is file and/or block checksums, regular readability tests, and sufficient redundancy for the inevitable repairs...
That means ZFS or BTRFS for anything important, with regular scrubs.

I've had all manner of RAID failures and filesystem corruption over the years, but I haven't seen a single damaged file in the decade+ I've been running ZFS on Debian/Devuan...
I do get the occasional:
"One or more devices has experienced an unrecoverable error... Applications are unaffected... Determine if the device needs to be replaced... Repaired [x]M in [y] hours with 0 errors"
type mail though, because all disks suck.
"desktop" disks suck hard, "green" disks suck harder, and "laptop" disks suck hardest of all. You get what you pay for, server (or "NAS") grade storage is worth every penny in reducing both risk and aggravation. Goes for HDD, SSD, or NVME, the price/performance/reliability triangle is the same.

GPU brand is utterly irrelevant for a webserver... having a GPU at all is irrelevant for that matter, the vast majority of webservers just use IPMI KVM or serial console.
Unless you need a GPU for media en/decoding or AI nonsense wasting energy, put those PCIe slots to a more constructive use like HBAs or more NICs.

There is a pretty good argument for AMD over Intel on the CPU front though, namely getting ECC support without the Xeon tax.

My take on storage would be ext4 on an (md)RAID1 of small SSDs for the OS and anything that doesn't play nice with COW filesystems (like the database if you CBF with filesystem tuning), and ZFS (mirror or RAIDZ) on 2 or 3 "NAS" grade spinners for data.

None of this is a substitute for backups of course, you should have those (and test them regularly) too.

As for other hardware, I'm not up with current pricing so I don't have any specifics, but in general: ECC memory and plenty of it, a not-bargain-basement motherboard, and somewhere to put at least 2 (preferrably 4 or 5) drives.
Everything else is negotiable, CPU load serving mostly static web content will be bugger all and disk latency won't matter much if you have enough RAM for a decent cache.
You'll want a quality PSU and a UPS with monitoring properly configured as well of course.

Update on these instructions - it says that partitions must end in a  non-zero digit and that's no longer true. I fixed it long ago. You can use md0 and if you do lvm you don't have to end the lv name with a digit. (e.g. /dev/mapper/nodigitshere would work.)
https://dev1galaxy.org/viewtopic.php?id=2323

The RAID idea for the OS drive is compelling, have to think about that one a bit, my first instinct (and what I do at home) is roll up a copy using Refracta Snapshot, then if anything craps out it's just a 10 minute install to get back up and running.

Yeah I haven't put together a website in years, not looking forward to that part, but that will be a few months from now anyway, first priority is getting it set up and serving. I do have some friends though in that field that might help me out when it's time. I really miss the old Yahoo SiteBuilder to be honest, it was actually a great quick WYSIWYG editor for throwing up sites fast.

One difference in your proposal compared to my home PCs is that my OS is also on a RAID1, so the OS can withstand a drive failure. That's saved me the time of having to reinstall and reconfigure the OS when one of the drives failed.

I think that's the limit of my home experiences that can apply to your project. From a brainstorming perspective, other issues that spring to mind are:

* Handling multiple client requests: If multiple client requests causes a lot of disk activity on the OS disk, maybe an SSD IS needed for the OS.

* Web page design: These days, web pages must be designed for mobile users, since everyone has a phone. I have no knowledge of modern web design.