The SAS 9 deployment page told readers to "unzip and place in the htdocs folder", which did not match what the archive actually did: frontend.zip was built from ./client/dist, so every entry carried a client/dist/ prefix and the unzip left an extra folder to navigate into.
dc/dc#147 changed the release job to zip from inside dist, so the archive now holds the frontend files at its root. This PR updates the page to match.
Changes (all in docs/dci-deploysas9.md)
Step 2: create the app folder and unzip the archive into it, naming the file that should end up there (index.html, alongside the images folder and the compiled asset files) with a concrete example path.
Step 3: the URL example is now <yourfoldername> - the folder the reader just created - rather than "unzippedfoldername".
Intro line: dropped "to the root of", which contradicted the subfolder instruction directly below it.
Verification
Checked against the released asset rather than the source:
42 entries, no client/ prefix, index.html and viya.json at the root, and images as the only subfolder - hence the wording above rather than a reference to an assets folder that does not exist.
Note this describes the archive as of v7.14.2. Releases up to v7.14.1 still carry the client/dist/ prefix, but the page documents the current release and the releases page carries the v7.14.2 notes.
The SAS 9 deployment page told readers to "unzip and place in the htdocs folder", which did not match what the archive actually did: `frontend.zip` was built from `./client/dist`, so every entry carried a `client/dist/` prefix and the unzip left an extra folder to navigate into.
`dc/dc` #147 changed the release job to zip from inside `dist`, so the archive now holds the frontend files at its root. This PR updates the page to match.
## Changes (all in `docs/dci-deploysas9.md`)
- Step 2: create the app folder and unzip the archive **into** it, naming the file that should end up there (`index.html`, alongside the `images` folder and the compiled asset files) with a concrete example path.
- Step 3: the URL example is now `<yourfoldername>` - the folder the reader just created - rather than "unzippedfoldername".
- Intro line: dropped "to the root of", which contradicted the subfolder instruction directly below it.
## Verification
Checked against the released asset rather than the source:
```
curl -sL -o frontend.zip https://git.datacontroller.io/dc/dc/releases/download/v7.14.2/frontend.zip
unzip -Z1 frontend.zip | grep -c '^client/' # 0
unzip -Z1 frontend.zip | grep -x 'index.html' # index.html
unzip -Z1 frontend.zip | awk -F/ 'NF>1 {print $1}' | sort -u # images
```
42 entries, no `client/` prefix, `index.html` and `viya.json` at the root, and `images` as the only subfolder - hence the wording above rather than a reference to an `assets` folder that does not exist.
Note this describes the archive as of v7.14.2. Releases up to v7.14.1 still carry the `client/dist/` prefix, but the page documents the current release and the releases page carries the v7.14.2 notes.
frontend.zip now holds the frontend files at their root (dc/dc #147, released in
v7.14.2), so unzipping no longer produces a client/dist folder to navigate into.
Step 2 now says to create the app folder and unzip the archive into it, naming
the file that should end up there. Step 3's URL example matches the folder the
reader created, and the intro line drops "to the root of" - it contradicted the
subfolder instruction directly below it.
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.
allan
The SAS 9 deployment page told readers to "unzip and place in the htdocs folder", which did not match what the archive actually did:
frontend.zipwas built from./client/dist, so every entry carried aclient/dist/prefix and the unzip left an extra folder to navigate into.dc/dc#147 changed the release job to zip from insidedist, so the archive now holds the frontend files at its root. This PR updates the page to match.Changes (all in
docs/dci-deploysas9.md)index.html, alongside theimagesfolder and the compiled asset files) with a concrete example path.<yourfoldername>- the folder the reader just created - rather than "unzippedfoldername".Verification
Checked against the released asset rather than the source:
42 entries, no
client/prefix,index.htmlandviya.jsonat the root, andimagesas the only subfolder - hence the wording above rather than a reference to anassetsfolder that does not exist.Note this describes the archive as of v7.14.2. Releases up to v7.14.1 still carry the
client/dist/prefix, but the page documents the current release and the releases page carries the v7.14.2 notes.