You are holding qvantum-web-<date>.zip,
built by qvantum-npi-dashboard/scripts/package_delivery.py.
What's in the zip
qvantum-web-<date>.zip
├── index.html ← a small "front door" linking the two areas (optional)
├── UPLOAD-INSTRUCTIONS.html ← this page
├── ai/ ← the "AI at Qvantum" site (tutorials, use cases, ambassadors)
└── dashboard/ ← the NPI/CPI Dashboard (project + software-release cards)The server web root should end up looking exactly like the inside of this zip:
index.html at the top, with ai/ and dashboard/ next to it.
If the server root already has its own landing page, just don't upload
index.html — upload only the ai/ and dashboard/ folders.Method 1 — Manual upload recommended for one-off updates
- Unzip
qvantum-web-<date>.zipon your computer. - Open your file-transfer tool to the server (the same SFTP / file-manager you use for other web uploads — e.g. FileZilla, WinSCP, or the hosting control panel).
- Go to the web root folder on the server (the folder that serves the site).
- Upload, replacing existing files:
- the
ai/folder → into the web root - the
dashboard/folder → into the web root - (optionally)
index.html→ into the web root
- the
- Open the site in a browser and check:
…/ai/shows the AI at Qvantum home…/dashboard/npi_cpi.htmlshows the project + SW-release cards
That's it. Uploading again later just overwrites the old files.
Method 2 — Scripted deploy dashboard only · needs SSH
The dashboard has a helper that pushes site/ over SSH.
From qvantum-npi-dashboard/:
# one time per terminal session: load your SSH key
ssh-add "$SSH_KEY_PATH"
# push the dashboard pages to staging
scripts/deploy_staging.sh quickServer login + path come from qvantum-npi-dashboard/.env (never committed):
| Variable | Meaning |
|---|---|
DEPLOY_USER / DEPLOY_IP |
server login + host (staging: ai.qvantum.local) |
DEPLOY_PATH | web-root path on the server |
This method covers the dashboard only. The AI site is hand-uploaded (Method 1).
Refreshing the content before you package
The two sites update differently:
- AI at Qvantum (
Q AI page/) — hand-edited HTML. Edit the files directly, then re-package. - Dashboard (
qvantum-npi-dashboard/site/) — generated, never hand-edited:/update-dashboard— re-reads the project text files inprojects/and re-renders./refresh-releases— re-pulls the software-release cards from Jira (read-only) and re-renders.- A backup runs automatically before every re-render.
Then rebuild the delivery zip:
cd qvantum-npi-dashboard
python scripts/package_delivery.py # → dist/qvantum-web-<date>.zip⚠️ Jira access note:
/refresh-releases uses an API token in
qvantum-npi-dashboard/.env. That token is tied to Jacob's account and stops working
after 2026-06-26 — reissue it under a still-employed account before then, or the
software-release cards will stop updating.