home-hosted 0.7.18 → 0.7.19

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -304,7 +304,7 @@ The first boot creates a `default` workspace.
304
304
 
305
305
  | | |
306
306
  | --- | --- |
307
- | global — `$HHOSTED_HOME/.hh/` | `settings.json` (listener, auth, TLS, host vitals, backups), `workspaces.json`, `.control-secrets.json` (password + API token, 0600), `.tls/`, `.ui/`, `.backups/`, `.logs/`, `run.json` |
307
+ | global — `$HHOSTED_HOME/.hh/` | `settings.json` (listener, auth, TLS, host vitals, backups), `workspaces.json`, `.control-secrets.json` (password + API token, 0600), `.tls/`, `.ui/`, `.backups/`, `.logs/`, `.proxy/` (the reverse proxy's engine, its config and state), `run.json` |
308
308
  | workspace — `.hh/<id>/` | `settings.json` (server defaults, logs, notifications, DDNS), `servers.config.json`, `.secrets.json` (Telegram + DDNS credentials, 0600), `.logs/`, `.state/` |
309
309
 
310
310
  </details>
package/docs/SERVERS.md CHANGED
@@ -65,6 +65,19 @@ environment (including `envFile`). Every supervised process also gets `HHOSTED_S
65
65
  `dataEnvs` is the one that pays for itself twice: the value is exported to the process *and* the path
66
66
  is picked up by Backups, so a data directory is declared once.
67
67
 
68
+ ### The "open server" link
69
+
70
+ An entry with a `port` gets a link in the UI, and **it follows the hostname you are reading the panel
71
+ at** whenever the entry binds `lan`. The panel's own report of a `lan` entry is this machine's LAN
72
+ address (`http://192.168.1.20:4991`) — true, but unreachable from outside that LAN, which is exactly
73
+ where a public hostname or a tunnel puts you. Reading the panel at `http://box.example:4999` therefore
74
+ links to `http://box.example:4991`.
75
+
76
+ The entry's port and scheme never change: a server port is plain HTTP whatever the panel is served
77
+ over, and the port belongs to the entry. Two cases keep the reported address instead, because both are
78
+ already correct: a `local` (or specific-IP) entry, which is reachable only at that address, and a
79
+ viewer already on the machine via `localhost`.
80
+
68
81
  ## A busy port
69
82
 
70
83
  Preflight runs before every start, so two servers cannot silently fight over one port.
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "home-hosted",
3
3
  "type": "module",
4
- "version": "0.7.18",
4
+ "version": "0.7.19",
5
5
  "packageManager": "pnpm@12.5.1",
6
6
  "description": "Self-hosted control panel that keeps your home-server processes alive: supervision, restarts, port conflicts, logs — and a UI you can replace.",
7
7
  "author": "NamesMT <dangquoctrung123@gmail.com>",