Technology

37735 readers

44 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

TheRtRevKaiser@kbin.social

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

submitted 1 year ago by mtset to c/technology

80 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

[–] pixxelkick@pathofexile-discuss.com 4 points 1 year ago

I would say specifically the hardest part for self hosting is the grok'ing of how SSL works and setting it up right with automatic renewal.

There's a lot of extra steps involved often.

Id also say understanding how routing works and why you need a reverse proxy is the other big one.