dc
3aae36f94d
Measured over the last 150 workflow runs on this forge: a pull request costs 56 runner-minutes (Build-and-ng-test 5.8m, Build-and-test-development 31.2m, lighthouse 19.3m), and when three pull requests are in flight the first job queues 47-69 minutes before it starts. - Build-and-ng-test publishes client/dist as an artifact and the Cypress job downloads it instead of running a second cold `npm run build` (1.6m each). Both jobs test the same bytes. - lighthouse: numberOfRuns 1 (lhci's default of 3 tripled the 13.6m audit to steady a median that only has to clear a fixed threshold), and the duplicate /view/usernav/groups entry is removed (17 unique URLs, not 18). - Cypress records no video in CI and takes screenshots on failure instead (`--config video=false,screenshotOnRunFailure=true`, CLI only so local runs and the demo recorder still record); the failure artifact carries screenshots as well as any video. - Both workflows detect whether client/ or sas/mocks/ changed and skip their expensive steps when neither did - a sas-only or docs-only pull request no longer pays 45 minutes for suites that cannot observe it. The gate is `!= 'false'`, so a missing step output runs the suite rather than quietly reporting green.
Data Controller for SAS
Control your manual data modifications!
Alternatives to Data Controller include:
- 💾 Developing / testing / deploying / scheduling overnight batch jobs to load files from shared drives
- 🔒 Opening (and locking) datasets in Enterprise Guide or SAS® Table Viewer to perform direct updates
- ❓ Asking a #DBA to run validated code after a change management process
- 🌐 Building & maintaining your own custom web application
- 🏃 Running #SAS or #SQL updates in production
Problems with the above include:
- Legacy 'black box' solutions with little to no testing, documentation or support
- End users requiring direct write access to critical data sources in production
- Upload routines that must be manually modified when the data model changes
- Breaches due to unnecessary parties having access to the data
- Inability to trace who made a change, when, and why
- Reliance on key individuals to perform updates
- Building bespoke ETL for every new data source
- High risk of manual error / data corruption
Data Controller for SAS® solves all these issues in a simple-to-install, user-friendly, secure, documented, battle-tested web application. Available on Viya, SAS 9 EBI, and SASjs Server.
An individual Viya deploy can be done in just 2 lines of #SAS code!
filename dc url "https://git.datacontroller.io/dc/dc/releases/download/latest/viya.sas";
%inc dc;
For a multi-user deploy, using a shared system account, please see deploy docs.
For further information:
- Main site: https://datacontroller.io
- Docs: https://docs.datacontroller.io
- Code: https://code.datacontroller.io
For support, contact support@4gl.io or reach out on Matrix!
Development
Lighthouse CI
This project includes automated Lighthouse performance and accessibility checks that run on pull requests. The checks ensure:
- Accessibility Score: Minimum 1.0 (100%) median score across all tested pages
The Lighthouse CI workflow:
- Sets up the development environment with SASjs server and mocked services
- Builds and serves the Angular frontend
- Installs Chrome and runs
lhci autorun(Lighthouse CI) against key pages - Uploads results as artifacts for review
To run Lighthouse checks locally:
cd client
npm install
npm run lighthouse
Configuration is in client/lighthouserc.js (URL list, desktop preset, Chrome flags, assertions).