Docker

Overview There are two main ideas behind this article: security and mobility. When you create your environment only on your server, laptop, Raspberry Pi, etc., it may be great, but without any backup, regular updates, or automation, it can easily become a SnowflakeServer anti-pattern.

Overview Nowadays, with multiple environments and many developers involved in a single project, it is difficult to properly test everything at a high level. Unit or any small tests are easy to run everywhere nowadays, on a local machine, in the cloud, in the pipeline, etc.

In my previous article I was talking about the usage of infrastructure within the code. Now I am going to take a few steps back and look into the depths of the azure cloud.

Introduction In this article, I would like to talk about the use of infrastructure within the code base. I will guide you through the pros and cons of infrastructure as code principles.

Add local SonarQube Start sonar qube with docker $ docker run -d --name sonarqube -p 9000:9000 sonarqube Insert sonar plugin to pom.xml (maven) <build> <plugins> <plugin> <groupId>org.sonarsource.scanner.maven</groupId> <artifactId>sonar-maven-plugin</artifactId> <version>3.6.0.1398</version> </plugin> </plugins> </build> Check with sonar quality of your code $ mvn sonar:sonar Insert into gradle project plugins { id "org.

l> Note Full code is not available. Only piece of code will be showed, so try to learn and create for yourself. Technology stack Python Python 3.7 Nameko framework Spring Boot 2.

Vault secures, stores, and tightly controls access to tokens, passwords, certificates, API keys, and other secrets in modern computing. Vault is primarily used in production environments to manage secrets. Vault is a complex system that has many different pieces.