docs: remove non-DC and low-value sections from v7.13.0 docs bundle
- deploy-viya: remove first-launch note, Deploy Checks section - admin-services: remove Licence Key Screen section - cas-tables: remove REPLACE Load Type subsection
This commit is contained in:
@@ -130,17 +130,6 @@ Now the services are deployed (including the service which creates the staging a
|
||||
* Admin Group - the members of this group will have full access to Data Controller
|
||||
* Compute Context - the context configured in Step 1
|
||||
|
||||
!!! note
|
||||
On the first-launch configuration screen, the **Groups** dropdown shows your own groups first, the **Contexts** dropdown groups contexts by their batch user, and a **Verify** button lets you confirm the startup service is running before continuing. If no admin groups are found, a clear message is shown instead of the screen hanging silently.
|
||||
|
||||
### Deploy Checks
|
||||
|
||||
The deploy process runs additional checks during installation to catch configuration issues early. For larger Viya environments, the deploy script is chunked for reliability. The compute context is also automatically corrected during deploy if needed.
|
||||
|
||||
!!! note
|
||||
A debug comment is added to the compute context during deploy. This is permanent - it is not removed by subsequent deploys.
|
||||
|
||||
|
||||
### Optimisation
|
||||
|
||||
At this point, every DC request will read the `services/public/settings.sas` file to get the DC library (and other) settings. To avoid these API calls (which will speed up the app) we can simply move this code to the autoexec. Steps as follows:
|
||||
|
||||
Reference in New Issue
Block a user