Technology

37747 readers

151 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

[email protected]

I don't think "command line hard" is the worst part of self-hosting. (beehaw.org)

submitted 1 year ago by [email protected] to c/[email protected]

45 comments fedilink hide all child comments

I've seen a lot of people saying things that amount to "those tech nerds need to understand that nobody wants to use the command line!", but I don't actually think that's the hardest part of self-hosting today. I mean, even with a really slick GUI like ASUSTOR NASes provide, getting a reliable, non-NATed connection, with an SSL certificate, some kind of basic DDOS protection, backups, and working outgoing email (ugh), is a huge pain in the ass.

Am I wrong? Would a Sandstorm-like GUI for deploying Docker images solve all of our problems? What can we do to reshape the network such that people can more easily run their own stuff?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 7 points 1 year ago

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.