dc/docs.datacontroller.io
3
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: improvements2
All checks were successful
Publish to docs.datacontroller.io / Deploy docs (push) Successful in 1m52s
Details

Browse Source
This commit is contained in:
allan
2025-06-04 14:53:03 +01:00
parent 7c2cc2628b
commit f090dc18ba
1 changed files with 7 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/deploy-viya.md
View File

@ -90,7 +90,7 @@ Unzip the frontend into your chosen directory (eg `/var/www/html/DataController`
Services are deployed by running a SAS program.
#### Streaming Deploy
#### Deploy Services: Streaming Deploy
Run the following in SAS Studio:
@ -100,7 +100,7 @@ filename dc url "https://git.datacontroller.io/dc/dc/releases/download/latest/vi
%inc dc;
```
#### Full Deploy
#### Deploy Services: Full Deploy
Run the following in SAS Studio:
@ -112,14 +112,18 @@ filename dc url "https://git.datacontroller.io/dc/dc/releases/download/latest/vi
### 4. First Run Configuration
Now the services are deployed (including the service which creates the staging area) we can open the Data Controller web interface and make the necessary configurations:
#### First Run Configuration: Streaming Deploy
At the end of the SAS log, there will be a link. Open this to perorm the configuration - such as:
At the end of the SAS log from Step 3, there will be a link (`YOURSAS.SERVER/SASJobExecution?_file=/YOUR/APPLOC/services/DC.html`). Open this to perorm the configuration - such as:
* dcpath - physical path for depleyment
* Admin Group - will have full access to DC
* Compute Context - should be a shared compute for a multi-user deployment
#### First Run Configuration: Full Deploy
Open https://YOURSERVER/DataController (using whichever subfolder you deployed to above) using an account that has the SAS privileges to write to the `appLoc` location.