Centralized_I-M_Database/SummerProject2026
7
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fixed issues w/ accessing website on other computers

Browse Source
This commit is contained in:
kevinbell
2026-07-22 16:26:12 -06:00
parent c1e453d962
commit 8bb76d8e6c
13 changed files with 266 additions and 68 deletions
Download Patch File Download Diff File Expand all files Collapse all files
dashboard/README.md
+27 -24
View File
@@ -25,6 +25,28 @@ URL; browsers will block the JSON module requests. To use another port:
PORT=8080 node dashboard/server.mjs
```
## Run a live demo on the same network
From the source-repository root, run:
```bash
node dashboard/server.mjs --lan
```
Stop any older dashboard process with `Ctrl-C` before starting. Or, from this
directory, run `npm run start:lan`. The server prints a **This computer** URL
and one or more interface-labeled **Other devices** URLs. Open the URL for the
shared Wi-Fi or Ethernet interface on the second computer; `0.0.0.0` is a bind
address, not the address to put in a browser. Confirm the in-app status reads
**Validated sample aggregates**, then stop the server with `Ctrl-C` after the
demo.
All data-contract and checksum validation remains enabled over LAN HTTP. When a
remote browser does not expose the SubtleCrypto digest API to the plain-HTTP
page, the dashboard uses its dependency-free SHA-256 implementation and still
rejects changed assets. The checks validate bundle consistency, not the
authenticity of a plain-HTTP connection, so use a trusted demo network.
Run the dependency-free contract checks with:
```bash
@@ -68,28 +90,9 @@ operational connection, or row-level prediction output. VINs, plates, ZIPs,
stations, technician identifiers, raw source JSON, credentials, and operational
records must never enter this directory.
## Publish through Bolt
## Public hosting is not required
Use a separate static Bolt project backed by a dashboard-only repository. Do
not import this source repository into Bolt.
1. Run `npm test` from this directory and confirm every contract check passes.
2. Create a clean dashboard-only repository or Bolt project.
3. Copy only the *contents* of `dashboard/` into that project, so `index.html`
is at the project root.
4. Confirm that private `data/`, `artifacts/`, `models/`, `.env` files, SQL,
notebooks, and database tooling are absent.
5. Preview the project. There is no install or build step; if Bolt requests a
preview command, use `node server.mjs` with `HOST=0.0.0.0` and let Bolt
provide `PORT`.
6. Verify all four views, the development-sample messaging on every view, and
that the in-app status reads **Validated sample aggregates**.
7. Use **Publish** only after the aggregate bundle completes privacy review.
Bolt hosting is the default; Netlify can instead be selected before the
first publish if desired.
See Bolt's official documentation for [Git
integration](https://support.bolt.new/integrations/git) and [publishing with
Netlify](https://support.bolt.new/integrations/netlify).
No publishing action is performed by this repository.
The current delivery path is the same-network live demo. No Bolt project,
public URL, dependency install, or build step is needed. If public hosting is
ever reconsidered, publish only a separately reviewed copy of this dashboard
directory—never the private source repository.