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

fix: deploy docs update for runastask
Publish to docs.datacontroller.io / Deploy docs (push) Successful in 1m5s
Details

Browse Source
This commit is contained in:
4gl
2026-05-15 13:27:48 +01:00
parent 1ca32b4b71
commit 874e045dff
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/deploy-viya.md
+3 -2
View File
@@ -80,7 +80,7 @@ To avoid giving users the ability to run code on that context (and shared system
Services are deployed by running a SAS program. Services are deployed by running a SAS program.
**Streaming Deploy:** **Streaming Deploy (BACKEND + FRONTEND):**
Run the following in SAS Studio: Run the following in SAS Studio:
@@ -90,7 +90,7 @@ filename dc url "https://git.datacontroller.io/dc/dc/releases/download/latest/vi
%inc dc; %inc dc;
``` ```
**Separated Deploy:** **Separated Deploy (BACKEND ONLY):**
Run the following in SAS Studio: Run the following in SAS Studio:
@@ -119,6 +119,7 @@ The following attributes may be updated in the index.html file. For streaming d
- `servertype` - should be SASVIYA - `servertype` - should be SASVIYA
- `debug` - can stay as `false` for performance, but could be switched to `true` for debugging startup issues - `debug` - can stay as `false` for performance, but could be switched to `true` for debugging startup issues
- `useComputeApi` - Setting `true` will give the best performance due to the use of [hot sessions](https://github.com/sasjs/adapter#using-the-compute-api) created client-side by the SASjs adapter. This is great for demo purposes, or when running a single user DC instance, however for typical enterprise use we recommend `false` or `null` so that the compute context usage can be restricted as described [above](/deploy-viya/#create-shared-compute-context) - `useComputeApi` - Setting `true` will give the best performance due to the use of [hot sessions](https://github.com/sasjs/adapter#using-the-compute-api) created client-side by the SASjs adapter. This is great for demo purposes, or when running a single user DC instance, however for typical enterprise use we recommend `false` or `null` so that the compute context usage can be restricted as described [above](/deploy-viya/#create-shared-compute-context)
- `runAsTask` - setting `true` will trigger jobs as Viya Compute Tasks. Be sure to increase the default expiry to 30 seconds (it is 5 by default) and set `useComputeApi` to `null`.
### First Launch ### First Launch