Deploy-your-own-SaaS: “only yours” cloud services for everyday needs
github.com
github.com
However, it should also be pointed out that it's also a deploy-your-own-unpaid-system-administrator-job. A lot of the value in SaaS products is the service provided of someone else maintaining it. The maintenance and security patching for running all this stuff, especially on the open Internet, that would quickly become a part time job.
So, I'd say that for most people with a limited time budget, it's worth the cost to simply find a high quality, paid SaaS provider for many of these services.
An example on from list: deploying your own email server and depending on it for your important communications is something that almost nobody should attempt on their own. Instead, most people should look to migrate from free providers that could do things like close your account/delete your data at any time, to paid ones that treat you like a paying customer.
I have my own media server, because when netflix removes friends, ill still be able to watch it. sure that means i have to buy the box set of friends for like 100$, which is 10 months of netflix into a single show. but i never have to worry about that going away. I'd rather have a raspberry pi with a webcam with motionEye letting me monitor my house than feeding private data into a company a dont trust.
This is also a hobby for me that has benefited me in my job on multiple occasions, and I only do it for services that I'm ok with downtime on (I've outsourced my email even though that's the data I would love to control the most, I'm not going to mess around with downtime on that). I absolutely wouldn't recommend any of these things for my grandma.
Also, "unpaid system administrator job" can be a bit of an extreme analogy. I do spend non-zero time working on these things... but because I was using this as a way to practice actual system admin things, they are generally set up for stability. there isn't much work to put into it after setup. Unchanged software rarely just suddenly starts breaking for no reason, especially when the traffic on it is low because there are only 2 people using the service. (again, I'm aware that self hosting email has all sorts of "you need to keep spam filter stuff up to date" weirdness, but I wouldn't advocate for that).
Other than email, anything on this list would be great for someone who wants to keep data in home, as long as they know the scope of how much free time they have vs their desired reliability.
Is this accessible online, or just at your house?
Also a prime example of a "downtime not a big deal" project. If it breaks, we just go back to the movie closet, and its no less convenient than how we used to do things (or just watch actual Netflix).
There sure are things that require quite a bit of maintenance, but personal e-mail servers is definitely in the other end of that spectrum.
Or is that too much responsibility/power?
If I had to choose between traditional cloud services and a friend providing best-effort service, I'm going to go with the former.
https://easydigitaldownloads.com/downloads/software-licensin...
That's how I see it anyway.
I suspect a single OS on metal with each of these in a Docker container would be more efficient, but I haven't played with containers before.
PiHole is so light-weight and relatively low-risk, you could easily run it on the same VM as Home Assistant if you'd like. I keep separate VMs for everything out of habit. I would isolate the LAMP site as much as possible, especially if it's publicly available—potentially even keeping it off of the same network as everything else.
Your use case might differ from mine quite a bit, but for me it was the best way to go. No server to babysit and everything "Just Works™".
I'm looking into Nextcloud and syncthing. A lot of people suggested Nextcloud. What do you like better about syncthing?
Must be why I like Go so much
https://github.com/sumdog/bee2
It's not really ready for general use, but I'm still glad I wrote it for myself. It hits all my use cases, taught me a lot about the Docker Engine API and helps me put up new self-hosted stuff really quickly. I might use it to deploy some stuff from this list.
I call it Joint Parallel, because that's the best term to describe that many cores can co-operate on the same memory at the "same time".
One-click install of many apps and services – but more impressively one-click upgrades as well. Nice, user-friendly, very little maintenance required. Self-hosting for people who don’t want to do system administration.
I’ve been running a Yunohost server for the past three years, adding and removing various services on the fly. Love to use it, and the great work of people behind this.
Our project ( https://github.com/amark/gun ) gets 1M+ downloads a month and can be self-hosted easily with a 1-click deploy into production.
Will try to make a PR when I get to my laptop. :)