Just released Site.js version 16.2.0

You can now run proxy servers in production.

To spin up a daemon that serves whatever is running over HTTP and WS at port :8080 on https://your.hostname, just do:

site enable :8080

(It will also automatically provision your Let’s Encrypt certificates the first time the service is hit and renew them as necessary.)

To update Site.js manually:

site update

(Production servers will auto update.)

· · Web · 2 · 8 · 7

And now with 100% more documentation :)

(Adapted from the full docs in the readme.)

@aral may I ask what is the proxy server used for?

@edgaras So say you want to run your own Owncast server. Out of the box, it runs insecurely on port 8080. If you want to run it securely, you have to use a proxy server to proxy requests at port 443 to port 8080 and back. So think of it, in this case, as being a security guard that relays information back and forth to someone in the house without allowing anyone into the house itself :)

@aral oh I see! Why tho all projects don’t run securely on 443? No proxy would be needed!

@edgaras Because it’s not trivial and requires certs (and because not everyone cares that it takes X hours to set up a server… not a problem for Big Tech, definitely). Until Let’s Encrypt there wasn’t even a way to automate it. So getting it to work seamlessly in Site.js was ~ 2 years of work and required me to write a auto Let’s Library from scratch (auto-encrypt).

@aral oh I understand it better now. Great work on auto-encrypt! The only problem with it if I have a small business and I don’t want to make it open-sourced, I cannot use it.

@edgaras Yep, that’s true. It’s for Small Tech, which is free and open. (That same clause keeps a large corporation from taking it and investing millions and not sharing back the improvements and crushing the original.) A tactic called “embrace, extend, and extinguish” that they could use later on if they ever see it as a threat.)

@aral “Large” as I see as a problem here. While small business suffer most from this. Not being able to use open code in a closed source (protecting IP). Big Tech can steal it and reengineer it if they want to. And small business are much more willing to support open source tools they use. Isn’t there more small business friendly license, encouraging people to build sustainable sources for living, instead of unicorns?

Sign in to participate in the conversation
Aral’s Mastodon

This is my personal Mastodon.