When it’s in a browser you don’t need to install anything on the local machine. I used to use Apache quack mole to access my machine at home from work when I was stuck in a cube all day. https://guacamole.apache.org/. - Source: Hacker News / 3 months ago

A pi4 is $35 + parts, and can do a PXE server as well... But it is the OS/kernel upkeep that always hits proprietary devices. Small recycled PCs can certainly work too, and reminds me of the https://guacamole.apache.org/ project. =3. - Source: Hacker News / 9 months ago

Have you ever heard of Guacamole? https://guacamole.apache.org/ That's one of my favorite obscure projects. - Source: Hacker News / about 1 year ago

Remote access for 10 people / end user access = Apache guacamole https://guacamole.apache.org/ - centralises access and audit and levels of access - MFA - HTML5 so all the enduser needs is a modern OS. Source: over 2 years ago

I use wakeonlan for all of my machines, and configure Guacamole to push the WOL packet, delay 30-300 seconds (depending on machine) and then give me a terminal session to the server. Source: over 2 years ago

Take a look at https://github.com/http-party/node-http-proxy , specifically their .web() helper. Source: over 3 years ago

I have been tasked with writing a proxy server that takes a clients requests and forwards it to a target server (normal proxy stuff). The client and the target are out of my control. The only change in the client is that the its requests to the proxy server instead of the target. Now, what I need to do is modify the response from target because the client expects it in a certain format and the server responds... Source: almost 4 years ago

What you're describing is a proxy server. If you wanted to use Node.js check out https://github.com/http-party/node-http-proxy. Notice that the examples there just forward the req though which potentially has identifying information like cookies, so you'll need to rework to anonymize. Should be straightforward. Source: about 4 years ago

There's several ways to have a blog path contain a separate setup from the marketing/product routes. One is to run a reverse proxy on the root domain to pull in separate routes for various services. https://github.com/http-party/node-http-proxy You can do rewrites at the server level for the root domain Or if the app on the root domain can do the routing for you (have done this before with a Rails app). - Source: Hacker News / over 4 years ago

Check the documentation of the http-proxy-middleware library (and of the node-http-proxy library, used under-the-hood) to learn how you can manipulate the proxied request & response. - Source: dev.to / over 4 years ago