this post was submitted on 09 Sep 2024
122 points (93.6% liked)

Selfhosted

40696 readers
396 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

I'm considering a business plan for people getting in to self-hosting. Essentially I sell you a Mikrotik router and a refurbished tiny x86 server. The idea is that the router plugs in to your home internet and the server into the router. Between the two they get the server able to handle incoming requests so that you can host services on the box and address them from the broader Internet.

The hypothesis is that $150 of equipment to avoid dozens of hours of software configuration is a worthwhile trade for some customers. I realize some people want to learn particular technologies and this is a bad fit for them. I think there are people out there that want the benefit of self-hosting, and may find it worth it to buy "self-hosting in a box".

What do you think? Would this be a useful product for some people?

you are viewing a single comment's thread
view the rest of the comments
[–] EliRibble@lemmy.world 6 points 3 months ago

I assume "SFF PC" means "Small form-factor personal computer".

The value add is not having to make a large number of technical decisions. IPv4 vs v6, which firewall rules to use, port-forwarding vs DMZ, flavor of Linux, partition scheme, filesystem type, application packaging system, and on and on. For many people they don't care about these decisions, they want "to put something on the Internet" and do it safely. While safety isn't a binary, and engineering is full of tradeoffs, an experienced practitioner can answer many of these questions reflexively and come out with good enough answers for some customers.

In the end the customer should be able to dig in and change whatever they want. But I want to see if flipping the decision dependency around will help. IE, start with stuff that works, then change things, rather than start with parts and make all the decisions before anything works.