This git repo is the single codebase for the whole project. There is a branch 'deploy' to publish changes to docker hub. (The master branch uses this dockerhubimage)
When started from 'master' branch all required resources are downloaded from docker hub. On 'Deploy' branch the build is done in a docker container and can be published to docker hub. All dependencies in the ASP.NET project are handled by nuget. The plantuml-service image comes as a precompiled container.
Docker is setup in a way that currently the app needs no configuration.
Docker-compose can setup the plantuml runtime dependency.
Build is done in 'develop' branch Release and Run are pretty much the same since no configuration takes place
Since all components are spawned in different docker containers, this should be fulfilled.
ASP.net web api applications force this behaviour
The 'PlantUMLController.Get()' Method is an async method. But currently only one plantuml instance is spawned, which, as far as ive tested does not support multiple requests at once. Spawning multiple plantuml instances would solve this problem.
Service is completely stateless, so it doesnt even leave any traces in the docker container Docker does the rest (hoefully)
The only difference between these stages is the docker compose file. All Code is managed by Visual Studio, so it applies to all the VS rules and works beautifully in the IDE. dev/deploy can both be handled through the VS UI.
ASP.Net Standard Logger does so by default.
No admin processes