This isn't the hard part of self-hosting, at least not anymore. In the comments here there are lots of examples of similar projects that solve basically the same problem (app selection and deployment). To make self-hosting "easy" we need to solve domain registration, DNS management, and port-forwarding configuration. This probably requires a project more like OpenWRT that includes an API-driven relationship with a re…
Makes me a little sad that it's been almost exactly 6 years since I made this comment: https://news.ycombinator.com/item?id=24475946 In that time I started a domain registrar, a free OpenID Connect login service ( https://lastlogin.net/ ), created the de facto list of tunneling tools ( https://github.com/anderspitman/awesome-tunneling ), and built a couple of my own tunneling tools (SirTunnel and boringproxy), all to…
Cloud in a Bottle: making self-hosting accessible to everyone
331–340 of 342 posts
Re: Cloud in a Bottle: making self-hosting accessible to everyone
#332Earlier quoted context omitted.
> One of my coworkers made a completely static portfolio website with a single page and used react. People love hating on react, but I mean this is pretty common. Raw is fine, but even in a "static" thing, you'll eventually go "ok now I want to reuse some text here.." Or have some common elements with x things shared. So I'm gonna have to write some hacky imperative JS? Or messy CSS? And what starts as static very ea…
Yeah pretty much this. I tend to use Astro but I think your point still stands. I wanted to make a basic online agenda in a few different formats for a Toastmasters club and though I could have used raw html and css to build it, but each agenda had slightly different layout that would have been a lot of copy pasting in html and lots of room for error. With astro and react islands it was fairly simple to implement.
Re: Cloud in a Bottle: making self-hosting accessible to everyone
#333Re: Cloud in a Bottle: making self-hosting accessible to everyone
#334Earlier quoted context omitted.
I don't like using Docker on a VPS because of the way it bypasses the firewall rules. It's such a pain that I avoid it altogether for anything public.
Docker doesn’t do that on my Fedora machine, nor on my arch machine. Did I set some setting somewhere that I forgot about? I’m also running rootless docker and podman so that might explain.
Even rootless docker usually pierce through that. Might be some setting in a podman, thought, never really worked with that.
Re: Cloud in a Bottle: making self-hosting accessible to everyone
#335Re: Cloud in a Bottle: making self-hosting accessible to everyone
#336Earlier quoted context omitted.
Admittedly this was not my castle. More of a $1.5/mo shed that I got just to try this.
That's a cheap shed, what's the provider and spec?
https://www.netcup.com/en/server/vps/vps-pico-g11s-iv-12m-nu...
Re: Cloud in a Bottle: making self-hosting accessible to everyone
#337Re: Cloud in a Bottle: making self-hosting accessible to everyone
#338Cloudron does something very similar (I'm a user): https://www.cloudron.io/
highly recommend!
Re: Cloud in a Bottle: making self-hosting accessible to everyone
#339So many docker app supervisors nowadays. I'm surprised there's no such thing as a self-hosted deployment spec. An opinionated docker-compose file (or similar) with well defined inputs, outputs, and requirements that works for the average use-case.