If you don't currently #SelfHost, but are interested in the idea, I'm curious to hear what's kept you from doing it?
If you *are* currently #selfhosting, what would have made it easier for you to get started?
Personally, I do, however I was surprised at how many common technical problems weren't automatically taken care of automatically. Most took a lot of research, experimentation and community support, even for someone like me who is pretty tech savvy and enjoys tinkering with computers.
Namely, on #Yunohost (which I otherwise ♥️ ) I ran into:
* No automatic port testing, to let me know why connections weren't getting through (I ended up using port testing websites)
* Nothing to detect/account for a dynamic IP address (ended up using #ddclient to auto-update the IP of my domain name)
While I worked all of them (except the last one) out, it increased the time to get to a working site from minutes to days. I didn't mind, but for many other people, it's likely a barrier.
I wonder how we could encourage automatic tools like these for *all* self hosting distros?
@Blort all of those are in our (absolutly stupidly gigantic) todo list of things to do but ... time is really a spare ressource :(
First one will probably the first to be done as Aleks is working on an automatic diagnostic system for domain configuration, this one is really the major self hosting blocking difficulty right now.
Second one will be for later, we have some lib that can talk to DNS register API but have yet to integrate it.
Last one we have no one that have this knowledge yet :(
@Blort This is something I've been thinking a lot about. I was able to manage self hosting because I know an awful lot about hosting web services. Even still, I ended up using Cloudron because I've got a day job.
I'd love to brainstorm ways to make the whole process easier.
@Blort I think that for me, it’s been (1) not having access to the router, (2) being lazy and (3) worrying about how reliable and fast the access to my self-hosted services would be.
I am self-hosting several projects on a simple server install which has accreted a ton of cruft over years and needs to be taken apart and rebuilt. The time and effort has me procrastinating.
What I want is an easy/tiny/fast proxy server, and then a separate box(es) with the hosted service(s), with panels including maintenance.
And to get there I would like a library of layman articles to explain the steps, which I would be happy to help write.
@Blort I self-hosted with Docker containers for a few years, but upgrading the containers was too hard. I switched to YunoHost and have been loving it. No port problems like you mentioned (maybe I should lock down my firewall, though)
Actually, it turns out my problem *wasn't* from port blocking. It was the first thing everyone on the Yunohost forums suggested though. There was no automated tool suggesting otherwise, so I still had to research which ports needed to be open and find a tool to test it to realize it was another problem.
I would have found the real issue sooner if it just tested and reported if necessary ports were open on install and on installing apps that needed new ports.
A system like that would also know which ports *should* be open and could then help you lock down your firewall by asking about ports that are open that it doesn't need.
@Blort Interested, but 1) I'm unsure of what hardware to get to get a cheap, green server for self-hosting and 2) unsure whether choosing 'between' ecosystems like Yunohost, Nextcloud and Freedombox will lock me out of/into certain apps for the things I want to host. (Example: I run Plex (Premium Pass) on an old Synology NAS which now refuses to update Plex because the hardware is deprecated, so I'm missing out on new features. Would like to avoid that kind of thing.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!