This project was generated with Angular CLI version 7.3.8.
Run ng serve for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.
Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.
Run ng build to build the project. The build artifacts will be stored in the dist/ directory. Use the --prod flag for a production build.
Pull requests and merges to master validate a non-published linux/amd64
image. Pushing an explicit Git tag matching v* publishes the same image for
linux/amd64 and linux/arm64, tagged with the Git tag. Stable version tags
also update latest; prerelease tags containing -, such as
v2.0.18-rc.1, do not.
The Angular bundle is built on BuildKit's native worker and copied into each
target-platform nginx image. This avoids running the Node build under QEMU.
Dependencies are installed reproducibly with npm ci; keep
package-lock.json synchronized with package.json. The Docker context also
excludes local dependencies, build output, Git metadata and test-only files.
The container build currently serialises Angular's stylesheet workers because
legacy component styles import the global Angular Material stylesheet; this
prevents intermittent Sass module-load loops in CI.
If the registry's latest alias must be rolled back, run the
restore-docker-latest workflow with an existing stable version tag and the
requested confirmation text. It retags the existing multi-platform manifest
without rebuilding or deploying the application; verify the resulting digest
before using it for a deployment.
Run ng test to execute the unit tests via Karma.
Run ng e2e to execute the end-to-end tests via Protractor.
To get more help on the Angular CLI use ng help or go check out the Angular CLI README.