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 must log in or register to comment.
Hi, I’m your customer base.
I’m a complete novice, no network or coding experience, but not afraid of computers either. I’m pretty worried about messing up something serious due to lack of knowledge.
In the end, I didn’t choose Synology or the like due to:
-
lack of robust community support. I’ve noodled around with Linux for years and learned that community support is essential.
-
price. I’d pay 10% or 50% more for a good pre-configured system, but not 3-4x more (which is just the general feeling I get from Synology)
-
lack of configurability. I’m still not sure what I would like to do (and be able). I know I want to replace some storage services, replace some streaming services, control my smart home, maaaaybe access my files remotely, and probably some other stuff. I may want to have email or a website in the future, but that’s not on my radar right now.
If there were some plug-and-play hardware/software solution that was still affordable and open, it would be a good choice for me.
I appreciate your thought process here! Where did you end up as far as self-hosting?
I’m currently about halfway through setting up a home server on an old/refurbished Dell PC. It has enough compute to transcode if needed, but no more. I’ll have to upgrade the storage to set up RAID. For software, I am running xubuntu, which offers the benefits of the great community and documentation of Ubuntu. It is very beginner friendly, but is a bit simpler and lighter than gnome. I’m running everything I can as Docker containers.
Nice. That’s similar to what I’m doing: Ubuntu LTS server running containers, orchestrated by Docker Compose, with a Traefik reverse proxy in front of everything. I’m curious about TrueNAS SCALE though, wondering if that would suit my needs.
-
I’m not in the market, but I’ve actually had similar thoughts of building a project on top of NixOS that’s focused on self-hosting for homes and small businesses. I recently deployed my own router/server on a BeeLink mini PC and instead of using something like OpenWRT, I used NixOS, systemd-networkd, nftables, etc.
DM me if you want to discuss more. I think the idea has potential and I might be interested in helping if you can get the business model right (even if it just ends up being some FOSS thing).
From reading the comments, I think you could be a lot leaner by selling the $100 setup fee, and telling people which “kit” is supported, and they buy that on their own.
That way you don’t have to deal with any of the physical infrastructure of buying/selling/storing hardware, and people can do some customization.
However I do think you’d need to put some restrictions in place so that people don’t buy cheap crap that doesn’t work and expect you to set it up and support it. They have to buy the kit or other compatible hardware.
I’m not sure what services you’d support, but personally I’d be interested in something like a personal introduction and setup of
- docker
- proxmox
- yunohost
- backups / restore (practice restoring)
- smb shared folder
- pihole / pivpn (can you have wire guard and openvpn setup at the same time for different uses?
Maybe migration of
- nextcloud
You could make different prices depending on what service they want, kind of like a bike stop.
I wouldn’t want a perpetual subscription, but I could stomach something like $100 setup + $5/mo for limited support for a year.
Best thing for me is that community support also exists for all these things too, but it’s hard to do it on your own sometimes.
150$ is rather ambitious for what you are describing as a custom made low power server. Managing to build something… Anything commercial out of new, hell even refurbished parts that has enough horse power to run anything more than a pihole/DNS server at this price point would be a challenge and a half. If you’re going refurbished/2nd hand, you’re likely gonna spend half of that on just shipping the parts to you.
I believe you are vastly underestimating the price of new low end parts and vastly overestimating the capabilities and availability of old micro servers. I’d say something like this would work at a price range of around 300~400$ (and even that’s ambitious imo).
And even then, that’s a NICHE audience you’d be targeting. It would be people who don’t wanna pay subscriptions, but also don’t wanna be bothered to spend a day or 2 figuring out how to set up a simple linux box on an old computer they have. I’m not saying that audience doesn’t exist, it’s just veeeeery niche.
Thanks, yeah, there’s a lot of work for us to do in testing hardware and understanding what a common workload (if such a thing exists) would need.
Do you have any particular evidence that causes you to think the audience would be niche or wouldn’t want to pay subscriptions? I can understand if this is just an opinion you hold, but if there’s data or experience behind it, that would be good to know.
Anecdotally, the majority of people I’ve seen who self host are doing it to replace subscription services. This ranges anywhere from piracy to libre office. So, they’re not gonna pay you a subscription for something they can do themselves.
The audience is niche because you’re aiming at a subset of a subset of a subset of people. You’re looking to sell this to someone who:
- Doesn’t want to pay for a service they can do by themself (self-hosters)
- Has the knowledge and desire to handle networking (no amount of preconfiguration will make them not have to set up which ports their services need while allowing freedom)
- But doesn’t have the time/energy to do it themself
- Can afford to shell out a rather large amount of money ($150 is a lot to many people, and as the other person brought up; you’ll likely end up selling it for much more than this after manufacturing costs)
- For a piece of equipment that is eclipsed by a 3 year old desktop computer from eBay
The amount of people who self host anything is already abysmally low - just look at the social media user count. There are more than twice as many people on r/pathofexile (which is already pretty niche) as on r/selfhosted. Obviously reddit isn’t the end-all be-all of representation in that way, but you can definitely get an idea of trends from it.
Well put. On top of the 5 points about the target audience above, in order to make a sale they also have to:
- Have heard of the product
- Decide to buy it (many will research competitive products)
- Spend the time to actually place the order
An interesting customer base might be small communal organisations. At our local scouts troop I had a discussion with a friend, who is also in IT. His idea (not fleshed out) was to provide small local organizations with a stack of already configured open source software to support the typical needs of such organizations (like a wordpress website, a nextcloud for file storage and common calender, limesurvey for surveys and event registration, mailman3 for mailing lists,…). Depending on the needs you could sell the initial setup process (your personal work in setting up and skill transfer) or ongoing support. Though such organizations normally don’t have much money to give away. So probably its not really worth your time financially (though probably really appreciated in the community).
How will you provide long term maintenance of their server for a one time payment of 150$?
How will you provide long term maintenance of their server for a one time payment of 150$?
My current thinking is the margin on the hardware would be intentionally low, essentially the cost of the hardware %+10 for configuring it a bit, installing NixOS, etc.
The business would survive on support and hosted services. Something like $20/month which gets you access to support to answer questions, help configure applications, troubleshoot issues, etc. Possibly rolling upgrades of your installed software on your behalf. Alerts on urgent security vulnerabilities. Could also handle tricky things like custom DNS (email servers, certificates) and off-site backups. I’m not totally sure what all would be included, but the goal is to make money while providing value, not build a garden or rent-seek.
So the problem with thin margins on the hardware side is what’s stopping a user from just installing their own OS once they figure out they can do the same thing you’re doing on the same hardware?
Nothing stops them, but that’d be fine. If they buy the hardware they should be able to do what they want with it.
$20 per month would be enough to discourage me. It’s another relatively costly computer-related subscription and I already feel like I’m losing a battle to keep those minimal. There would have to be some very clear benefits for that price.
There would have to be some very clear benefits for that price.
Agreed, it would need to be very clear, and additionally we’d need to plan that a certain percentage of customers would grow out of a basic support offering, either by becoming experts or by growing their install size and complexity.
$20 per month would be enough to discourage me. It’s another relatively costly computer-related subscription and I already feel like I’m losing a battle to keep those minimal.
Understandable. Is there a price you think would be reasonable? What would you want for that price?
Raspberry pi was able to do it with $35.
Raspberry Pi is not a server. That people use it as one does not mean it’s fit for purpose.
While true I feel like your comment misses the point. A raspberry pi is just a computer, not a magic solution box that’s kept maintained and updated by some guy. Their product isn’t a service, it’s just the device.
The fact that it’s an option that even remotely works is my point. They sell hardware. They don’t support software. The community does that. There is something to be gained from having a uniform platform for learning self hosting responsibly.
A Raspberry pi isn’t particularly great at any one thing. It’s greatest strength comes in bundling everything you need in a box at an affordable price. Once you know where your pain points are then you can build/design a system that overcomes those shortcomings.
Having a starter kit would be an easy way to get more people in the space. Would it cost $35 of course not. Level1Techs made their KVM to meet their own requirements and then the community benefits. To me, this project has that kind of energy. Or at least the potential for it.
Isn’t that basically just a commercial NAS? Go buy a Synology NAS, or get fancy w/ TrueNAS. You don’t need an entry-level enterprise-grade router at all, you can just plug the NAS in anywhere and you’re golden. You can usually install a few services like Plex/Jellyfin or HomeAssistant alongside the data storage if you like.
If that’s not going to work for you, you probably have a good idea of what will work for you. For me, a tiny x86 server isn’t going to cut it, because I want a beefier CPU to run CI/CD for my programming projects, so a beefier, modern CPU is quite valuable. That’s totally overkill if all you want is a simple streaming setup with 1-2 transcoded streams.
So I think there are two main markets here:
- just give me something that works - these will flock to pre-configured solutions, like Synology or TrueNAS
- I want something specific - they’ll DIY components together to build their own custom solution
The only other group I can think of is the group that can’t afford 1 and doesn’t know enough to do 2, but I really don’t think that’s a particularly big group, and they’d be better off reusing something they already have instead of getting some off-the-shelf solution.
I could absolutely be wrong here, that’s just my $0.02.
Isn’t that basically just a commercial NAS?
Is it? I haven’t bought one, nor have I built a TrueNAS box. I’ve heard from folks that run applications on a NAS, particularly VMs and containers, but my understanding is that your price-per-unit-compute is really high since that’s not what it’s optimized for. I’ve got an old Zyxel NAS, it’s quite low-end, and I can’t run anything beyond NFS/Samba/audio streaming.
you can just plug the NAS in anywhere and you’re golden.
Do they have some kind of VPN or TURN system? I’m expecting that customers will want to access the device outside of their LAN.
For me, a tiny x86 server isn’t going to cut it, because I want a beefier CPU to run CI/CD for my programming projects, so a beefier, modern CPU is quite valuable
How beefy? Multiple CPU? If you could buy 4 boxes and have them load balance would that be interesting, or do you have a strong preference for single-box compute?
I could absolutely be wrong here, that’s just my $0.02.
Thanks, your $0.02 is exactly what I’m looking for!
price-per-unit-compute is really high
Well yeah, they’re optimized for storage. And if you’re starting from nothing, you’re going to need storage.
Synology is your budget home cloud, and it’s just good enough to handle basic cloud tasks and small-scale service hosting. If you grow out of it, you leave the Synology NAS for purely data storage, and add another box for heavier compute.
TrueNAS, on the other hand, is usually overkill for a home NAS setup because it’s designed for small-ish business use-cases, so it has a lot more CPU and RAM than you’d need when you only have a handful of users in a home setting. So it can probably handle any CPU workload you throw at it, within reason. It probably wouldn’t make a great compiling cluster, but it would do really well hosting things like NextCloud. If you’re looking for transcoding, you need to check the hardware and drivers on FreeBSD (maybe it’s not an issue, but it’s good to check first).
Do they have some kind of VPN or TURN system?
How would the router help with that? If you’re behind CGNAT, you’ll need something external regardless. If you’re not behind CGNAT, pretty much any router on the planet can do port fowarding, and many can handle a network-wide VPN if that’s what you’re after.
I’m behind CGNAT and I have a VPS that hosts my VPN and routes all traffic using HAProxy over the VPN to my internal devices, and my internal devices maintain a persistent connection to the VPN. It sounds complicated, but it’s really just two config files that I’d be happy to share if anyone is stuck. I do have a Mikrotik router, but it’s not needed for any of this, I only use it for static DNS routes so I don’t hit the WAN when accessing my services by their domain names (and VLAN for ZeroTrust shenanigans, but again, not needed at all). If I didn’t have that option, I could always just host a DNS server right on my NAS and do the same thing (any router can set the DNS server over DHCP).
How beefy? Multiple CPU?
No, I’m not that productive. I just want it to run builds of my Rust projects, and those can take some time. So 6-8 recent-ish cores is plenty. Right now I’m using a Ryzen 1700, and once I upgrade my PC, I’ll move my Ryzen 5600 to it. I want my builds to finish somewhat quickly without interfering with other services on the machine (e.g. if I’m running a build while we’re watching a movie, I don’t want the movie to stutter).
If my project grows (i.e. I get outside contributors), I’ll need higher specs.
And yeah, my preference for a single box is storage space. My NAS sits on my desk, and I’d really rather not get a rack setup. More machines means higher power and more space. I do have a couple of Raspberry Pis around for specific use-cases (e.g. one on my TV for RetroPie), but I’d really rather not have a handful of PCs running 24/7. Electricity is pretty cheap where I live, but even then, I’d rather not waste power just because I can get a good deal on servers. My single box uses something like 40-50W, and once I upgrade to my 5600, idle draw will drop another 10-20W (I have a 20-30W floor due to the drives).
I’m just skimming this thread, but paragraph 2 is basically fact. I’m on my second synology box, the UI is simple and I want reliability, I don’t want shit to break because of a git push on some bullshit tool. But recently I snatched a Lenovo server and threw proxmox and Debian on it, and also got a vps.
The synology is actually pretty capable, especially if it can do docker, and if you are willing to venture into (as a beginner) copy/pasting commands from the internet into the task scheduler as a half-assed way to get at the terminal, it can do literally everything that I want. But I’m a geek, why should I keep a stable, reliable system as my only machine? :p
My synology does files, some docker stuff. Lenovo does a couple docker stuff, BOINC since it’s just idling most of the time, and docker for game and related hosting on my vps. Hell, this entire thing could be ‘just add a network folder, and install docker and dockge/portainer’.
Though (paragraph 3) I tried and didn’t like TrueNAS. Maybe it’s because the synology does it already, I was just exploring, but it has that ‘foss feel’ where you have no idea what you are doing, even when you know what all the pieces do, and it just kinda is like ‘here you go, figure it out’ and leaves. I remember the UI being equally… ‘designed by a programmer’ let’s say. It might be powerful but oof, slick it ain’t.
For once I’m #1 in something 🥳
I think this needs to exist, but as a community supported system, not as a commercial product.
Pick a set of open technologies - but not the best, lightest weight, just pick something open.
Come up with a security architecture that’s reasonably safe and only adds a moderate amount of extra annoyance, and build out a really generic “self-hosted web hosting and VM company-like thingy” system people can rally around.
Biggest threat to this, I think, is that this isn’t the 90s and early 2000s any longer, and for a big project like this, most of the oxygen has been sucked out already by free commercial offerings like Facebook. The technical family friend offering to self-host email or forums or chat no longer gets gratitude and love, they get “why not Facebook?”
So… small group effort, resistant to bad actors joining the project to kill it, producing a good design with reasonably safe security architecture, that people can install step by step, and have fun using while they build and learn it.
We already have that, the first problem is we have like a dozen of them, a few are even well supported. The second problem is that usually the technical knowledge required to set up the systems are still lower than the technical knowledge required to keep it running.
I’ve been struggling to wrap my head around a good security architecture for my mspencer.net replacement crap. Could I bug you for links?
I figured out a while ago to keep VM host management on a management VLAN, and I put each service VM on its own VLAN with heavy, service-specific firewalling and a private OS update repo mirror - but after hearing about ESXi jackpotting vulns and Broadcom shenanigans, I’ve gotten really disheartened. I’d love some safe defaults.
It sounds like you’re getting into the keeping it running phase.
First, going back to your previous comment, self-hosting email is difficult. It’s not hard for a small provider to end up blacklisted and you’re probably kind of just done at that point and it will feel very unfair. I get that it’s a fun set of technical challenges, but you couldn’t pay me enough to help someone self-host email.
Second, guessing, but it sounds like you may be trying to expose your services directly and doing a lot to make that work which goes against what most would recommend for hosting your own services. Big companies don’t expose their intranet like that, follow their example. Almost every guide or system is going to warn against that. If you’re going to host more than one thing, highly recommend focusing on minimizing entry points and looking into a VPN-like solution for accessing most if not all of your services. Still spend time on securing your intranet, but most of your risk is going to come from how hard it is for people to get past the front door (or doors).
Thank you for your reply, but to be clear, I’m not looking for individual details to be spelled out in comments. What you said is absolutely correct, thoughtful, and very helpful. But emotions are running a little high and I’m worried I’ll accidentally lash out at someone for helping. Apologies in advance.
But do you have any links? Beyond just the general subjects of security architecture, secure design, threat modeling, and attack surface identification, I’d love to see this hypothetical “generic VM and web application housing provider in a box” come with a reasonably secure default architecture. Not what you’re running, but how you’re running it.
Like, imagine decades in the future, internet historians uncover documentation and backups from a successful generic hosting company. They don’t necessarily care what their customers are hosting, their job is to make sure a breach in one customer’s stuff doesn’t impact any other customer. The documentation describes what policies and practices they used for networking, storage, compute, etc. They paid some expensive employees to come up with this and maintain it, it was their competitive advantage, so they guarded it jealously.
I’d want to see that, but (a) a public, community project and (b) now, while it’s still useful and relevant to emulate it in one’s own homelab.
If I can get some of that sweet, sweet dopamine from others liking the idea and wishing for my success, maybe I can build my own first version of it, publish my flawed version, and it can get feedback.
I think this needs to exist, but as a community supported system, not as a commercial product. … The technical family friend offering to self-host email or forums or chat no longer gets gratitude and love, they get “why not Facebook?”
I think this is a great point, it doesn’t help much to create a business that ends up with the same incentives and the same end-game as the existing systems.
So… small group effort, resistant to bad actors joining the project to kill it, producing a good design with reasonably safe security architecture, that people can install step by step, and have fun using while they build and learn it.
That is precisely what I’m looking to build. I don’t want to get rich, I want people without 10 years of industry experience to get some of the benefits we have all been able to build for ourselves.
I think a possibility is a series of open source anvil or nixos scripts that you can run on most hardware with minimal changes, in an extendable architecture of some kind to add or remove functionality and they perhaps get maintained by the community or some structure of the kind of Linux distributions.
This could enable people with minimal skills set up and maintain a reasonably useful but secure environment just by changing a few variables.
nixos scripts
What’s a nixos script?
Nixos is an os that’s defined by its config stored in .nix files. Everything is defined here all the software and configurations. Two people with the same script will have the exact same os.
Any changes you make that aren’t in the scripts won’t be present when you reboot.
You could maintain a very custom linux distribution (kinda) by just maintaining these config scripts.
So a user wouldn’t need to install all required software and dependencies. They could get a nixos and the self-host config and adjust some settings and have a working system straight after install.
A viable alternative is Guix, which uses Scheme for its scripts and could also use the Hurd kernel instead of Linux, but works the same.
I’m probably an ideal candidate for something like this but I’d much rather have someone walk me through setting my own thing up, rather than them handing me a bunch of preconfigured stuff that leaves me just as clueless.
If it came bundled around a bunch of DIY guides explaining the hows and the whys, it’d be far more appealling
If it came bundled around a bunch of DIY guides explaining the hows and the whys, it’d be far more appealling
Interesting, so if you got hardware and it came with guides, what kind of guides would you want? I would assume something layered. At the top is just “I want to install these 5 apps and use them, I don’t care how it works” and in the middle is “I’m ready to SSH into the router and create some VLANs for fun” at the bottom is something like “I want to flash my own firmware with appropriate certificates for secure boot and my own root chain of trust on the server hardware”.
The guides, basically a quick and dirty walkthrough on setting it up, hopefully a few explanations about things, and a handful of common troubleshooting tips. Also pointers to a handful of communities that have helpful info in case something obscure pops up.
Basically, teach a man how to fish, as opposed to giving him a couple.
I think a lot of people who would otherwise dabble with a DIY home server never try because it’s pretty technical (beyond typical ‘build a pc’ stuff) so I think the education that would come with the hardware would be appreciated by many. Help them get their foot in the door by making the dive a little less scary. Nothing too over the top but point them to the places where people hang out discussing the more technical crap for when that day comes
I could see this being a use case for a NixOS deployment where your company manages the configuration file and versioning of the system, as well as providing support. Over time, I’d you’re diligent about building documentation based off of each support request, you’ll end up with a personalized guide. And if your customer decides take a break or quit entirely, they have a configured system that doesn’t lock them in into something too esoteric.
Disclaimer: I only know of Nix, never used it because I just don’t manage that many machines to be worth my while to learn it.
Hard agree. In fact, I think there’s a market for JUST the guides. It’s true that there’s a TON of guides out there already, from old blogs to YouTube, but the issue is: all of them start or end with: “your use case might differ, so perhaps this solution isn’t for you.” Or “make sure this setup is compatible with your specific hardware”
For example: I want to set up some sort of backup/cloud storage type system. Well there’s about 1400 ways to accomplish that. I can easily just grab one and go, but I’ll always wonder- should I have done this a different way? Would my life be easier/more secure if I chose a different set up?
So offering hardware that is compatible with whatever “stack” of services included would be a huge plus. Sorta like getting a raspberry pi and following a specific raspberry pi tutorial- you know the issues you get aren’t gonna be due to incompatibility.
I think it really boils down to the scale of one’s home lab- are you just tinkering to get some skills and make something cool? Or are you hoping to do something much much bigger? Different software solutions fit those extremes differently.
Sorry, got off rambling there. I guess I’ve been down the home lab hardware/software wormhole for too long these last few weeks.
Sorry, got off rambling there. I guess I’ve been down the home lab hardware/software wormhole for too long these last few weeks.
Not at all, I found your comment insightful. What you’re describing to me sounds more like a business of consulting with people rather than getting access to a knowledge base. One of the things I’m curious to learn is if there is a body of people out there that give up with self-hosting because they don’t want to learn everything, but just want to create something that works, and our resource are optimized for training professionals.
I’ve thought more on this yesterday, and I think my issue is-
I don’t want something that ‘just works’, I want to BUILD something that ‘just works’
The distinction is that I don’t want to buy premade solutions. I want to make them. Not because of the customizability, but because the fun is in the building. Think Lego- hundreds of people build the exact same product in the end, but why are they sold in pieces? Just assemble the damn things and sell them complete (with markup). You think more people wanna buy that?? I’d bet against it.
What’s the value-add over just buying a SFF PC?
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.
Probably not much for people on a self hosting community, but those that want to get away from subscriptions and steal your data as a service cloud providers that might need some reassurance that they’ll have a working system.
No. People who want the benefit of self housing without worrying about hardware will rent a vps or something simpler. The hard part of hardware isn’t the purchase, it’s the maintenance.
Also, why the separate router?
I agree with this. Self-hosting requires the user to understand their network, their software, how it all interacts.
If you provide a hardware product and call it a solution, people are going to expect a turn-key solution like a plug-and-play router.
You’re going to end up supporting a bunch of newbies who, by no fault of their own, can’t tell you an error code in the console let alone whatever UI you give them.
I think a better solution would be a course that walks newbies through self hosting.
People who want the benefit of self housing without worrying about hardware will rent a vps or something simpler.
That’s certainly an option. I think of dedicated hardware as working for several different people, some of which care a great deal about not using a VPS provider because they don’t trust them with their data, or don’t trust them to be around for a long time, or don’t trust them not to raise the prices.
The hard part of hardware isn’t the purchase, it’s the maintenance.
I’m inclined to agree, but I’ve been doing hardware for a long time as a hobbyist and I sometimes forget how far I’ve come. It sounds like you might be somewhat like me in that regard. I’m often surprised when people see assembling system parts and flashing an OS as a complex, inscrutable task.
What do you see as the hard part of maintenance? Scheduling time to do it? Unexpected errors or failures?
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.
Why would I need a separate router for that? I’d need to configure the main router anyway.
I would absolutely want the extra router because most people have one from their service provider. For self hosting, you want an additional router with your own software.
Which problem(s) are you trying to solve? The networking issue of firewalls and port forwarding? The admin tasks of installing and configuring applications? The task nobody does of maintaining software and keeping it up-to-date?
Which problem(s) are you trying to solve? The networking issue of firewalls and port forwarding?
Within the scope of this question, yes. Also properly configuring IPv6, though that’s just to achieve the same things that port forwarding enables.
The admin tasks of installing and configuring applications?
That’s also on my list, but I was trying to keep the question focused. Do you think the answer makes a difference? In other words, if it was just networking would it be not worth it, but networking and application management would make it worth it?
I don’t think the networking part is part that needs solving. Modern AP/routers are pretty easy to configure and setup securely. Dunno - I’m definitely not in the target audience for what you’re doing though.
I would be happy if I could pay you to just set up and periodically check my setup. I only say that because I would probably want to put together something that cost more than $150. But I am absolutely overwhelmed by what I don’t know. Every tutorial I read gives me more questions than answers.
I just want to self host, share it with a close circle of friends, and keep everyone else’s noses out of my business.
Would you rather pay a higher price per single instance ($100 to fix something you broke on accident) or pay a lower constant price ($10-$20/month) like insurance?
Would you rather get help in the form of a conversation, a custom script someone wrote for you, or by giving admin access to the company to directly fix things?
I would be willing to pay an initial setup fee followed by some maintenance fee. I would expect the initial fee to be significant due to a custom setup/requirements. (I am talking just setup, not cost of hardware/ physical installation).
Unique home network with 2 managed switches.
Self hosted security DVR, automated computer backup, photo backup, network drive for document storage and then self hosting a Jellyfin server along with a torrent service.
(I am sweating just thinking about trying to set that up)
Storage will be a RAID setup where I can just upgrade by throwing a new drive into an open slot and replace (as necessary) existing drives by just swapping them out and server automatically handles the data management.
I have a VAGUE idea of what that takes
Maintenance would cover service calls to resolve problems due to security updates/patches, end of life upgrades, normal planned maintenance type of stuff.
User caused issues should be extra :) (i.e. I was just trying to install a Minecraft server)
Couple hundred bucks, at least, for setup. And that seems cheap.
I would pay $10-20 a month for a maintenance fee after an initial setup fee.
I would MUCH rather give my money to an individual sysadmin than a corporate megalith that will use my membership to force an arbitration clause to any future service of theirs I use. Fuck the mouse. Fuck em all. I tried to do it right and that still want enough for them.
I am absolutely overwhelmed by what I don’t know. Every tutorial I read gives me more questions than answers.
I felt that in the very core of my being.
Looking at my setup, sometimes I look back and wonder how tf I’ve made it this far. Dozens, if not hundreds, of hours of searching, reading, watching YouTube tutorials, and I feel like little has stuck with me. If the boot drive in my proxmox server takes a shit on me before I manage to figure out how to properly back everything up before that inevitable failure occurs, I’ll be back at square one (as in, still clueless and destined to spend dozens/hundreds of hours getting things set back up and configured).
I can say that I am a bit more familiar with the linux terminal now than I was a couple years ago when I first started, so there is some learning and growth taking place. But I’m still just a wee lad still trying to figure out how to simply stand up on my own. And heaven help me if an actual problem arises.
If I don’t have to fail to understand another “Docker’s not that bad | complete beginners’ tutorial” video, I’d sign up.
Although any commercial business will be dead or the new problem to avoid in 15 years.
Docker’s secret that most “getting started” tutorials seem to miss is docker-compose.yml. Who wants to type these long-ass commands to start containers? I always just create a compose file, and then
docker compose up -d.Dockerfile is for developers, you shouldn’t need more than a docker-compose.yml for self-hosting stuff.
Although any commercial business will be dead or the new problem to avoid in 15 years.
This sounds like an interesting point, could you expand it a bit? Are you saying that there’s no way this kind of business will last that long, or if it does it’ll become something bad?
Do you still need help with docker?
