A Continuos Practices / DevOps tech demo for a modern, cloud based web application.
Featuring a single-page application (SPA) written in Aurelia and served via lighttpd and a web API, written in DotNet Core 3.1 and Quarkus, deployed via docker containers.
The setup also demonstrates:
- Unit tests (with report generation and coverage tracking)
- [WIP] Integration tests
- Benchmarks
- [WIP] E2E tests
- [WIP] Load tests
- [WIP] Stress tests
- Docker Image Build
- [WIP] Docker image upload to registry
The Web API is provided either as .Net Core 3.1 project or as native build with Quarkus + GraalVM.
$ git clone git@github.com:NetzwergX/Primes.git
$ cd Primes/
$ pushd dotnet-rest-api/
$ dotnet publish -c Release
$ popd
$ pushd aurelia-spa/
$ npm install
$ popd
$ docker-compose up
(The MIT License)
Copyright © 2020 Sebastian Teumert <https://sebastian.teumert.net>
In order to use dotnet benchmark,
you need to run dotnet tool install -g BenchmarkDotNet.Tool.
$ git clone git@github.com:NetzwergX/Primes.git
$ cd Primes/rest-api/
$ dotnet build -C Release
$ dotnet benchmark ./Prime.Service.Benchmarks/bin/Release/netstandard2.0/Prime.Service.Benchmarks.dll --filter * --runtimes net472 netcoreapp3.1 Mono
To change the artifact folder:
$ git clone git@github.com:NetzwergX/Primes.git
$ cd Primes/rest-api/
$ dotnet benchmark ./Prime.Service.Benchmarks/bin/Release/netstandard2.0/Prime.Service.Benchmarks.dll --filter * --runtimes net472 netcoreapp3.1 Mono --artifacts="./path-to-artifact-folder/"
You can also run dotnet tool restore
and then use dotnet dotnet-benchmark ...
Run npx eslint ./src --ext .ts,.tsx --report-unused-disable-directives
in Prime.UI/
If you are using the project in VS Code and open the root folder, ESLint will
search the config files in the root folder. To properly run from Prime.UI/,
add "eslint.workingDirectories" : ["Prime.UI/"] to your settings.json
(for Microsofts ESLint plugin).
This repo contains a workspace settings.json with the proper ESLint configuration.