Lettuce eat lettuce

If you’re very comfortable with containerization, networking, and security practices, plus you are a pretty decent full stack web dev, sure.

It’s pretty trivial to set up a separate business internet line from your local ISP. Depending on the volume of traffic, a basic load manager and reverse proxy, combined with strong firewalls and container safety would be sufficient for most SMB needs.

You don’t need much power to host a basic website. Setting up a local box with a low-impact distro, Docker, and some solid control-plane MGMT software should be plenty to host several dozen SMB websites.

There are a lot of technical and even legal considerations though. Do these small businesses need a web app on their site? Do they need a storefront? What about member-only content locked securely behind an authentication layer? Does your local ISP have rate limitations? Does your city/state/country have restrictions on offering business services like that? What is your liability if your setup gets hacked and your client’s data is stolen/exposed?

Ultimately, you have to answer the question: Why shouldn’t those businesses just go with an easy pre-made hosting solution like Squarespace, Wix, etc? Not saying there aren’t good answers to that, but from a business perspective, the businesses will want to know that.

As with anything in business, ask yourself, what are you able to offer that they can’t get easily somewhere else? I used to work for a tiny MSP that offered in-house data backups. Our clients paid a good chunk of money to have us backup their data to our own servers. I didn’t say anything at the time, but our clients could have gotten much more secure and faster backup services for cheaper using something like Backblaze or Synology’s S2 cloud backups.

Don’t find yourself unable to clearly and concisely explain to your clients what you can give them that they cannot easily get somewhere else. If it’s purely the principle of the thing, that’s totally valid, but make sure that’s what you’re selling to them, and also what they are looking for.

Dang, that’s too bad. Hopefully one day!

I love localsend.

Works on Linux, Android, iOS, Windows, and Mac. It is basically an OS agnostic Airdrop.

It’s FOSS, so you can go to the Github and build from source for OpenBSD, but I have no idea if that would work.

Immutable distros are great for applications where you want uniformity for users and protections against users who are a little too curious for their own good.

SteamOS is a perfect use case. You don’t want users easily running scripts on their Steam Decks to install god knows what and potentially wreck their systems, then come to Valve looking for a fix.

Immutable distros solve that issue. Patches and updates for the OS roll out onto effectively identical systems, and if something does break, the update will fail instead of the system. So users will still have a fully functional Steam Deck.

If you’re not very technical, or you aren’t a power user and packaged apps like Flatpaks are available for all your software, then go for it. I prefer to tinker under the hood with my computers, but I also understand and except the risk that creates.

Immutable distros are a valuable part of a larger, vibrant Linux ecosystem IMO.