resume384

Making the internet more useful in the area of concise to the point information without sidetracks would be a big improvement. How is your startup approaching the reading problem on the web?

Pull might also be a nice way to address the 'right now!' problem. Some, likely most information can wait till you're ready and doesn't need be available till then.

Yeah, I'm thinking more and more the same, I'm beginning to think we need a dual function web.

Static web, and run as an app web.

I kinda have this by running with javascript off (this solves all sorts of other issues, though much of the web doesn't work that could work.) When I need to 'run as app' I allow js for that one visit.

Good idea. Done.

Currently all access goes out to the net and returns via the edge node. Works, but we can improve this. The ability to go LAN to LAN is an advantage of home hosting and some (many of the newer) web api services require https to work. One possible approach, on todo, adds a name server service on the LAN which maps your domains locally when you're LAN side, and a mechanism added which forwards certs generated on the edge node Caddy instance to be used on the LAN Caddy instance.

Hey, repo poster here. The requirements are if one wishes to be able to follow all the directions completely. Depending on your drivers you may or may not want Cloudflare. Some advantages of Cloudflare are privacy (hiding your actual server IP (if you proxy all the addresses,)) caching (if you expect a lot of traffic,) nice API control of name server functions, and it's free. But, you trade that for unencrypted man in the middle, certainly an understandable deal-breaker for certain situations. Cloudflare can be skipped and your domain mapped directly to your edge server IP using your registrar dns panel.

I recently decided to make a simple hand built personal private multi-host capable cloud system. I'm really liking how things are going and would like input. What input does the hacker news community have for this project? The intent is to create a repository maintaining contemporary resources for handcrafting and maintaining in a manageable way a personal multi-host capable private cloud system that's accessible internally and externally. P.S. I've found similar projects I'd like to go over in more detail, many of which I looked into briefly but not found in them just what I'm going for, if you're interested in them there's a link to most at the bottom of the git readme. Thanks HN!

Pushing your ingress out to a full internet node simplifies behind the NAT/dynamic IP hosting. Once you have a static IP and no NAT or port restrictions it's much easier to run a from home personal cloud system.

..that might go something like this...

Raspberry Pi at home running docker containers with a reverse proxy like Nginx or Caddy. The Pi is set to automatically connect to the wireguard service once it has a network connection. The hosting server with the external public IP forwards port 80/443 browser traffic to the Pi sitting in your home LAN. Your domains can be mapped through Cloudflare to the public IP of your external server for an extra layer of privacy and caching. Requests to your Pi webserver reverse proxy through other containerized services on the Pi or to other hosts within your private home network running services like Wordpress, GOGS, Express Node app, Verdaccio (npm cache/proxy,) pretty much anything. Things get even more interesting if you run a reverse proxy on the remote server. It's also great to have a static public address by which to reach and manage your internal servers via ssh.