New docs/downloads.md page (Installation section, after System Requirements), plus links from dci-deploysas9.md.
The page
Table of every release asset and what it is for (frontend.zip, sas9.sas, demostream_sas9.sas, viya.sas, viya_noweb.sas, viya_noweb.json, sasjs_server.json.zip, SHA256SUMS), linking to the SAS 9 / Viya deployment pages for the deployment routes.
"Verifying a download": download asset + SHA256SUMS into the same folder, then sha256sum --check SHA256SUMS --ignore-missing. Includes the Windows certutil -hashfile <file> SHA256 alternative for single-file checks.
"What the checksum proves": byte-for-byte match with what the pipeline uploaded (corrupted/tampered downloads), and an explicit statement that it is not a signature - the hashes travel with the files, so they protect the download path, not the release itself.
A short "Integrity inside SAS" note pointing at the reviewable source and code docs.
Cross-links
dci-deploysas9.md links to the new page in the three places it sends the reader to the releases page (sas9.sas, frontend.zip, demostream_sas9.sas downloads).
Why
Companion to the dc/dc PR that publishes SHA256SUMS and a verification section with each release - the docs make the same check discoverable from the deployment instructions.
Verification
mkdocs build passes; nav entry, sitemap URL (https://docs.datacontroller.io/downloads/), page title and cross-page links verified in the rendered output. No customer material; plain ASCII punctuation.
## What
New `docs/downloads.md` page (Installation section, after System Requirements), plus links from `dci-deploysas9.md`.
### The page
- Table of every release asset and what it is for (`frontend.zip`, `sas9.sas`, `demostream_sas9.sas`, `viya.sas`, `viya_noweb.sas`, `viya_noweb.json`, `sasjs_server.json.zip`, `SHA256SUMS`), linking to the SAS 9 / Viya deployment pages for the deployment routes.
- "Verifying a download": download asset + `SHA256SUMS` into the same folder, then `sha256sum --check SHA256SUMS --ignore-missing`. Includes the Windows `certutil -hashfile <file> SHA256` alternative for single-file checks.
- "What the checksum proves": byte-for-byte match with what the pipeline uploaded (corrupted/tampered downloads), and an explicit statement that it is not a signature - the hashes travel with the files, so they protect the download path, not the release itself.
- A short "Integrity inside SAS" note pointing at the reviewable source and code docs.
### Cross-links
`dci-deploysas9.md` links to the new page in the three places it sends the reader to the releases page (sas9.sas, frontend.zip, demostream_sas9.sas downloads).
## Why
Companion to the dc/dc PR that publishes `SHA256SUMS` and a verification section with each release - the docs make the same check discoverable from the deployment instructions.
## Verification
`mkdocs build` passes; nav entry, sitemap URL (https://docs.datacontroller.io/downloads/), page title and cross-page links verified in the rendered output. No customer material; plain ASCII punctuation.
Adds /downloads to the Installation section, listing what each release
asset is for and how to verify a download against the SHA256SUMS file
the release pipeline publishes (sha256sum -c, plus certutil for
Windows). The SAS 9 deployment page now links to it wherever it sends
the reader to the releases page.
mkdocs build passes; nav, sitemap and cross-links verified in the
rendered output.
The integrity section claimed SAS writes nothing to disk outside the
appLoc. The appLoc is the SAS Folder the stored processes or jobs are
deployed into (metadata), so it is not a disk location at all - the only
physical location the deployment programs write to is the Data Controller
location (dcLoc) configured at first launch.
allan
merged commit 90b374a52e into main2026-09-25 19:35:08 +00:00
allan
deleted branch docs/release-download-verification2026-09-25 19:35:08 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What
New
docs/downloads.mdpage (Installation section, after System Requirements), plus links fromdci-deploysas9.md.The page
frontend.zip,sas9.sas,demostream_sas9.sas,viya.sas,viya_noweb.sas,viya_noweb.json,sasjs_server.json.zip,SHA256SUMS), linking to the SAS 9 / Viya deployment pages for the deployment routes.SHA256SUMSinto the same folder, thensha256sum --check SHA256SUMS --ignore-missing. Includes the Windowscertutil -hashfile <file> SHA256alternative for single-file checks.Cross-links
dci-deploysas9.mdlinks to the new page in the three places it sends the reader to the releases page (sas9.sas, frontend.zip, demostream_sas9.sas downloads).Why
Companion to the dc/dc PR that publishes
SHA256SUMSand a verification section with each release - the docs make the same check discoverable from the deployment instructions.Verification
mkdocs buildpasses; nav entry, sitemap URL (https://docs.datacontroller.io/downloads/), page title and cross-page links verified in the rendered output. No customer material; plain ASCII punctuation.