Files
dc/sas/mocks/sasjs/sasjsconfig.json
T
dc a4ad4cba28
Build / Build-and-ng-test (pull_request) Successful in 5m42s
Lighthouse Checks / lighthouse (pull_request) Successful in 21m28s
Build / Build-and-test-development (pull_request) Successful in 28m23s
fix(ci): correct server-ci webSourcePath and build frontend before mock deploy
The server-ci target streams the Angular frontend (CONTRIBUTING.md documents
http://localhost:5000/AppStream/clickme/), but webSourcePath was
"`../../../../client/dist". The leading backtick makes the first path segment
literal, so it happened to resolve to <repo>/client/dist by accident; the
correct value relative to the sasjs project root (sas/mocks) is
../../client/dist.

The real problem was that CI job 2 never built the client, so client/dist did
not exist when the mock services were deployed: the deploy logged
"webSourcePath: <repo>/client/dist present in 'streamConfig' doesn't exist"
and streamed no frontend, while the job still passed. Build the production
frontend before deploying the mocks so the streamed app is actually produced.
2026-09-27 18:48:03 +00:00

42 lines
1.1 KiB
JSON

{
"$schema": "https://raw.githubusercontent.com/sasjs/utils/main/src/types/sasjsconfig-schema.json",
"defaultTarget": "server-mihajlo",
"syncFolder": "sasjs",
"targets": [
{
"name": "server-ci",
"serverUrl": "http://localhost:5000",
"serverType": "SASJS",
"httpsAgentOptions": {
"allowInsecureRequests": true
},
"appLoc": "/Public/app/dc",
"streamConfig": {
"streamWeb": true,
"streamWebFolder": "web9",
"webSourcePath": "../../client/dist",
"assetPaths": [],
"streamServiceName": "clickme"
}
},
{
"name": "server-mihajlo",
"serverUrl": "https://sas.4gl.io:5002",
"serverType": "SASJS",
"httpsAgentOptions": {
"rejectUnauthorized": false,
"allowInsecureRequests": true
},
"appLoc": "/Public/app/dc"
},
{
"name": "dcdemo",
"serverUrl": "https://sas.4gl.io:5006",
"serverType": "SASJS",
"httpsAgentOptions": {
"allowInsecureRequests": false
},
"appLoc": "/Public/app/dc"
}
]
}