v3.0.2

Author: perki

nodejs/.gitignore

@@ -1,3 +1,4 @@
 node_modules
 certs/*
-!certs/.gitkeep
+!certs/.gitkeep
+./config.json

nodejs/README.md

@@ -13,21 +13,21 @@ Any subdomain of `*.backloop.dev` points to `localhost`!
 **Exception:** `backloop.dev`, which points to a page where you can download the certificates.
 
 
-## Why ?
+## Why?
 
-**backloop.dev** solves [mixed-content](https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content) issues when developing a WebApp or Backend on local environement while accessing ressources on remote HTTPS sources. 
+**backloop.dev** solves [mixed-content](https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content) issues when developing a WebApp or Backend on local environment while accessing resources on remote HTTPS sources.
 
-The issue is often raised by the [same-origin policy](https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy) mechanism that restricts the loading of resources from another origin unless this can be allowed by sending correct [Cross-Origin Resource Sharing (CORS)](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) headers. 
+The issue is often raised by the [same-origin policy](https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy) mechanism that restricts the loading of resources from another origin unless this can be allowed by sending correct [Cross-Origin Resource Sharing (CORS)](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) headers.
 
-Which anyway will fall-back on the must-have "non-mixed-content" (No HTTP & HTTPS) 
+Which anyway will fall back on the must-have "non-mixed-content" (no HTTP & HTTPS).
 
 But making requests to **HTTPS APIs** from **HTTP** sites on **localhost** would not be possible without changing security options on your browser, which is why **backloop.dev** provides SSL certificates with a full loopback domain, to let anyone benefit from a signed certificate on **localhost**.
 
 ## Where are the certificates?
 
-Certificates are not bundled with the npm package, but downloaded and updated from [backloop.dev](https://backloop.dev) at installation and runtime, or manually with `backloop.dev-update`. To specify in which directory the certificates should be stored set the environement var `BACKLOOP_DEV_CERTS_DIR`.
+Certificates are not bundled with the npm package, but downloaded and updated from [backloop.dev](https://backloop.dev) at installation and runtime, or manually with `backloop.dev-update`. To specify in which directory the certificates should be stored, set the environment variable `BACKLOOP_DEV_CERTS_DIR`.
 
-If the certificates are outdated they are checked and updated at boot.
+If the certificates are outdated, they are checked and updated at boot.
 
 ## Usage
 
@@ -42,19 +42,88 @@ Add `-g` to use `backloop.dev` and `backloop.dev-proxy` globally.
 
 (Don't forget to prefix commands with `npx` if not installed globally.)
 
-Start a webserver serving the contents of a directory on `https://whatever.backloop.dev:<port>/`:
+#### Static file server
+
+Serve the contents of a directory on `https://whatever.backloop.dev:<port>/`:
 
 ```
 backloop.dev <path> [<port>]
 ```
 
-Start a proxy on `https://whatever.backloop.dev:<port>/`  
-Note: proxy will add `x-forwarded-proto: https` to headers. This is to support express-session and other services and advertise it was served in https. 
+Example:
+```bash
+backloop.dev ./dist 4443
+# Server started on port 4443 serving files in './dist'
+# Open https://myapp.backloop.dev:4443/
+```
+
+#### Reverse proxy
+
+Proxy requests from `https://whatever.backloop.dev:<port>/` to a backend.
+Supports `http://` and `https://` targets, with optional base path.
+Note: adds `x-forwarded-proto: https` to headers for express-session and similar services.
+
+```
+backloop.dev-proxy <target> [<port>]
+```
+
+Where `<target>` can be:
+- `http://host[:port][/path]`
+- `https://host[:port][/path]`
+- `host[:port]` (legacy format, defaults to http)
+
+Examples:
+```bash
+# Proxy to a local dev server
+backloop.dev-proxy localhost:3000
 
+# Proxy to an https backend with a base path
+backloop.dev-proxy https://localhost:8443/api 4443
 ```
-backloop.dev-proxy <target host>[:<target port>] [<port>]
+
+#### Multi-host config mode
+
+Serve multiple hostnames from a single instance, each with its own static files or proxy target:
+
+```
+backloop.dev --config=<config.json>
 ```
 
+Config file format:
+```json
+{
+  "port": 7654,
+  "hostnames": {
+    "app": { "path": "./dist" },
+    "api": { "proxy": "http://localhost:3000/v1" },
+    "admin": { "proxy": "https://anotherwebsite.com:8443" }
+  }
+}
+```
+
+This starts a single server on port 7654 where:
+- `https://app.backloop.dev:7654/` serves static files from `./dist`
+- `https://api.backloop.dev:7654/` proxies to `http://localhost:3000/v1`
+- `https://admin.backloop.dev:7654/` proxies to `https://anotherwebsite.com:8443`
+
+Paths are resolved relative to the config file location.
+
+**Path-based routing** is also supported. Use `hostname/path/` keys (trailing slash required) to route different URL prefixes to different handlers on the same hostname:
+
+```json
+{
+  "port": 7654,
+  "hostnames": {
+    "tom/static/": { "path": "./public" },
+    "tom/": { "proxy": "http://localhost:3000" }
+  }
+}
+```
+
+Here `https://tom.backloop.dev:7654/static/app.js` serves `./public/app.js`, while `https://tom.backloop.dev:7654/api/users` proxies to `http://localhost:3000/api/users`. The longest matching prefix wins.
+
+#### Certificate update
+
 Manually force update of the certificates:
 
 ```
@@ -63,7 +132,7 @@ backloop.dev-update
 
 ### Certificate files
 
-You can download the certificates files on [backloop.dev](https://backloop.dev) for your own usage.
+You can download the certificate files on [backloop.dev](https://backloop.dev) for your own usage.
 
 ### From a node app
 
@@ -94,7 +163,7 @@ httpsOptionsAsync(function (err, httpsOptions) {
 });
 ```
 
-Or with promises.
+Or with promises:
 
 ```js
 const https = require('https');
@@ -111,7 +180,7 @@ const httpsOptionsPromise = require('backloop.dev').httpsOptionsPromise;
 })();
 ```
 
-The following is not recommended as it will crash your app if certificates are expired. Thus it will refresh them for your next boot ;). 
+The following is not recommended as it will crash your app if the certificates are expired. It will however refresh them for your next boot ;).
 
 ```js
 const https = require('https');
@@ -173,23 +242,31 @@ export default defineConfig({
 ```
 
 Now `npm run dev` will be served on `https://whatever.backloop.dev`
-There is a ViteJS plugin that does the very same [vite-plugin-backloop.dev](https://www.npmjs.com/package/vite-plugin-backloop.dev).
+There is also a ViteJS plugin that does the same: [vite-plugin-backloop.dev](https://www.npmjs.com/package/vite-plugin-backloop.dev).
 
-## Security 
+## Security
 
 What if `*.backloop.dev` DNS A and AAAA entries are not pointing to `127.0.0.1` and `::1` but to another IP (malicious ones)?
-Then your HTTPS requests will not end-up on your machine, but on this malicious servers. 
+Then your HTTPS requests will not end up on your machine, but on these malicious servers.
+
+Even if this is very unlikely to happen, you may want to be on the safe side by adding `<what you need>.backloop.dev` in your `/etc/hosts` file.
+
+```
+127.0.0.1 localhost whatever.backloop.dev ...
+::1 localhost whatever.backloop.dev ...
+```
 
-Even, if this is very unlikely to happend, you may want to be on the safe side by adding `<what you need>.backloop.dev` in your `/etc/hosts` file.
+## Testing
 
 ```
-127.0.0.1 localhost whatever.backloop.dev ... 
-::1 localhost whatever.backloop.dev ... 
+npm test
 ```
 
+Uses Node.js built-in test runner (requires Node.js 18+).
+
 ## Contributing
 
-`npm run lint` lints the code with [Semi-Standard](https://github.com/standard/semistandard).
+`npm run lint` lints the code with [neostandard](https://github.com/neostandard/neostandard).
 
 Pull requests are welcome.
 

nodejs/bin/update.js

@@ -3,4 +3,4 @@ const updateAndLoad = require('../src/check').updateAndLoad;
 
 (async () => {
   await updateAndLoad(true);
-})()
+})();

nodejs/config.json

@@ -0,0 +1,7 @@
+{
+  "port": 7654,
+  "hostnames": {
+    "tom/static/": { "path": "./" },
+    "tom/": { "proxy": "https://perki.com" }
+  }
+}

nodejs/eslint.config.js

@@ -0,0 +1,3 @@
+const neostandard = require('neostandard');
+
+module.exports = neostandard({ semi: true });