If you’re afraid of the CLI then you probably didn’t be hosting anything complex yourself. The CLI is one of the least complicated parts of server administration.

the hardest part is doing backups and updates. Repeat after me:

no backup, no pity,

updates neglected, compassion rejected.

Getting a decent VPS is pretty cheap. Email is the enormous problem. Even if your VPS provider allows outgoing email, your IP address will be flagged and blocked by all mailservers everywhere for the crime of not being Google or Microsoft, or not having a full-time person working 24/7 to satisfy the people in charge of blacklists. You can pay someone else to send your email, but that’s going to cost you as much or more as the VPS you’re using to host your entire app.

It’s not the command line that’s hard but the lack of proper documentation and tutorials that makes things hard.

Do we actually need people afraid of CLIs to host anything? Sounds like a hassle.

It’s not even about gui.
If you want to self host you get yourself a pile of software of community-level quality (i.e “it works good until it doesn’t” is the best outcome) you need to care about. This means constantly being involved - updating, maintaining, learning something, etc, and honestly it’s time-consuming even for experienced sysadmins.

Look at installing Gentoo, or Arch, or Alpine vs Ubuntu. There’s no technical reason we can’t make Gentoo installation GUI. It’s just going to be very very tedious. Orders of magnitude more tedious.

At the same time Gentoo allows you to customize WAAAAY more things during its install than Ubuntu.

So specifically for lemmy - yeah we can probably make some sort of default AWS image where you just select it when spinning up new VM and you’re up and running. But what if you want something slightly different? Maybe you prefer MySQL instead of Postgres. Or Apache instead of nginx, or maybe you want images hosted on a different machine. Suddenly it’s the install GUI author’s responsibility to support install of 10 different databases, or load-balancers, or something else, and each one has their own GUI options. Then someone else wants 11th database added and it has 10 more custom options…. Oh and now someone else is asking for a DigitalOcean image instead… or and now someone’s asking for Docker image… You see where this is going.

The sad truth is that non-techy types will never want to host something themselves unless there’s a reason why doing so is better. I’m not just talking about better the way you and I think of better, either. Nobody really cares about privacy or security or ownership of data. A lot of people like to say those things matter but until it’s as easy to host your own email as signing up for gmail, and doing so provides all the fringe benefits you get with Google, you’re not going to get completely non-technical people self hosting.

You’re right, though. As part of this, there needs to be a way to have an all-in-one package that defaults to enabling the things you’re talking about. There are a lot of plug-n-play methods of self hosting any number of things, but the hard part of hosting is doing it right and securely.

To be honest, the command line is an important tool, that when you are able to use correctly, will give you a better understanding of a lot of the inner workings of a machine.

The commandine might be intimidating at first, but I personally think not as big of a hurdle to think about replacing it with anything.

Most people that I know that at first were afraid of the command line but tried to get into it, now don’t want to go back. Working with the cli is so efficient that it’s hard to go back to GUI’s.

Edit: don’t get me wrong. I do love a good gui! And I am all for creating usefully GUI’s, also for tech jobs. But I don’t see a point in replacing the job you do in the cli with a GUI.

I don’t really have patience for people’s willful ignorance. The command line isn’t hard, you’re just dumb. (edit: Not “you” specifically.)

As for NAT and SSL, you don’t need to fiddle with those directly. You can use Wireguard for routing and encryption. For personal use I tend to host my servers as Tor hidden services which gives them routing, encryption, and anonymity. Client side SSL certificates are also something people underestimate here; you can use those for simultaneous encryption and authentication.

Outgoing email can be hard, but since you control the sender and the receiver, you don’t need to go through the public internet’s spam filters. You don’t even necessarily need to use SMTP, you can just drop the files in the maildir and sync that across the systems.

Technology is complicated. Period. Anything that “seems” simple is in reality extremely complicated underneath the hood. A GUI is nice as long as it works. But if for some reason it doesn’t, you’re shit out of luck.

One-click would definitely lower the bar to entry but I have to admit the concept makes me uncomfortable. While it cloud eliminate those problem it creates the issue of creating thousands of server administrators who really don’t understand the platform that they are now responsible for. Infrastructure and security IS hard because it’s not just about getting the right syntax, it’s understanding the concepts so that not only does it work, it works safely and reliably.

I’ve seen quite a bit of bad troubleshooting going on as newcomers have sought to set up their instances. It doesn’t help that the current docker-compose in the Lemmy repository is outdated and doesn’t work out of the box. More than a few “this worked for me” solutions that I’ve seen may have gotten things working, but broke fundamental security principles that may or may not come back to bite the administrators later.

We need an actual official setup tutorial that is kept up to date. The existing documentation for the Docker setup process is extremely bare-bones, and it doesn’t even link to the right config files. There are some unofficial tutorials out there that are better, but they’re outdated and they link to the wrong config files too.

I’ve been working on getting Matrix Synapse running on my NAS, and the CLI hasn’t been my problem. I’m a programmer, and CLI doesn’t scare me; but the other issues you mention are all new to me, and getting a web service set up so people outside my local network can access it but without leaving me open to bad actors is wicked stressful.

The biggest problems end up being that I need to work with the soup of technologies, and there’s no one place to do all the things. I’ve got TWO routers (because my internet comes through one, and I run my LAN and wifi off one I trust better) which means I’m double-NATed, which is apparently the root of all evil; I can use Cloudflare to tunnel to my NAS, but I can’t accept simple (CNAME) redirects from a family member’s domain to one of my subdomains without paying Cloudflare $200/month, so that means I’m back to dealing with the double-NAT, and then I have to learn setting up TLS, which sounds like it’s simple, but still it’s jimmy way another thing to screw around with and another thing I could screw up on accident.

I could pay for a VPS, but that to me defeats a lot of the point of “host your own” federation when some company could be subpoenaed for copies of all their hosted accounts or something. (Yes, I could get subpoenaed for my data just as easily, but it takes more work to subpoena a thousand people than one company for a thousand people’s accounts.)

Anyway, I’d love to see things evolve to where it’s easy for newbies to host their own private instances of everything.

Personally, I’d love a drop-in tool that runs more like a temporary server while it’s running, syncing federated data you missed while your device was off; and only serving your data when it’s on. Likely with some kind of redirect service/NAT punchthrough so other clients can find you…

…but I think we’re a long way off from being able to do that.

So you want non-technical people to set up botnet members?

There’s this thing called ‘money’ which people who can’t do a thing give other people who can do the thing well to make them do the thing.