resume384

Many good projects listed here.

Ask HN: What's your quarantine side project?

https://news.ycombinator.com/item?id=23170881

Instructions to build yourself a private self-hosted full-stack personal cloud system.

https://github.com/technomada/cloud-from-scratch

- organization: https://humanetech.com/ https://builders.mozilla.community/

- projects: https://inrupt.com/ https://ipfs.io/ https://blockstack.org/

- technology: dnssec ip6

- application: https://d.tube/

- ideas: a not-for-profit web.

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.

If anyone is interested in full stack self hosting, I recently started a cloud from scratch resource here.

https://github.com/technomada/cloud-from-scratch

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.

Control is one element of self hosting, albeit full control may be difficult to obtain and also maintain speed and privacy. Pushing your ingress out to an edge node affords interesting properties. One of which is privacy (keeps your home ISP IP hidden from the public.) A service like Cloudflare gets you the same for browser traffic, a service like hoppy can work for all ports, email, ssh, voip, etc. Control can and perhaps should be implemented not at the channel layer but through cryptographic means such as authentication and end to end encryption.

Hey cool! Nice job, I'm been working on nearly the same thing, been using it for a bit and find this pattern has really nice properties, like it's great to access my servers at local network speed (ssh, file copy, etc really fast,) having the option to easily move the server to another network, adding something like cloudflare to the mix I'm thinking one could host quite well from home. What is the use case that inspired you to build it? I'm really curious to see what interest and dynamics you find. It would be great if you could post an update as things progress.

A multi host capable personal cloud computing platform. Using primarily existing technologies and influenced by the "Arch Way" (Simplicity, Modernity, Pragmatism, User centrality, Versatility) the design requires a small amount of technical attention and allows a wide range of functionality. To make it immediately useful, I'm creating a few simple applications and utilities: data, social, personal apps.

SEEKING WORK | US | Remote

I build cool things with Vanilla JavaScript, Web APIs and direct DOM manipulation.

hn20ef@synchsys.com | 415-854-6590

  Location: USA
  Remote: Preferred
  Willing to relocate: Open to the possibility.
  Technologies: Modern JS, HTML5, CSS3, Web APIs, Node.js, Docker, Linux
  Résumé/CV: request
  Email: hn20e@synchsys.com
  Phone: 415-854-6590

Nice insight. Recently posted my take after jumping into the industry head first after going it independently for decades....

https://www.linkedin.com/pulse/let-me-open-you-adam-m

https://news.ycombinator.com/item?id=22820905

SEEKING WORK | US | Remote

Hey there. Are you in need of a developer who enjoys building Vanilla JS and browser native WebAPI based applications?

I fell in love with coding after first setting eyes on a programmable device decades ago and have been banging out code just about as long.

TECH: Linux, Modern JavaScript, HTML5, CSS3, Node.js, Docker

Reach out, I'm excited to hear about your project. Open to unconventional arrangements.

resume384@synchsys.com

  Location: USA
  Remote: Preferred
  Willing to relocate: Open to the possibility.
  Technologies: Modern JS, HTML5, CSS3, Web APIs, Node.js, Docker, Linux
  Résumé/CV: shorturl.at/CDKLP
  Email: resume384@synchsys.com
  Phone: 415-854-6590

  Location: USA
  Remote: Preferred
  Willing to relocate: Open to the possibility.
  Technologies: Modern JS, HTML5, CSS3, Web APIs, Node.js, Docker, Linux
  Résumé/CV: https://bit.ly/2IoWhJb
  Email: resume384@rbx.email

Open to unconventional offers and arrangements, let's talk... reach out via email, or text/call 415-854-6590.

SEEKING WORK | USA | REMOTE

Hey there. Are you interested in a coder who is comfortable writing VanillaJS and browser native Web API based applications?

I've been coding for the love of it since first laying eyes on a programmable device decades ago, I've been banging out code in the web industry just about as long.

FAV TECH: Linux, Modern JavaScript, HTML5, CSS3, Node.js, Docker.

Reach out, I'm excited to hear about your project. I'm open to unconventional arrangements.

resume384@rbx.email