ditkrg/guidelines-and-instructions
4
0
Fork 0
mirror of https://github.com/ditkrg/guidelines-and-instructions.git synced 2026-01-23 06:16:39 +00:00
Code Issues Packages Projects Releases Wiki Activity

Header: ### Version Control and Repository Management

Browse Source
This commit is contained in:
Brusk Hamarash 2021-10-02 22:54:18 +03:00
parent 8709a14c5e
commit ef4a4df144
No known key found for this signature in database
GPG Key ID: 509F705341F6504F
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
Software-Development/README.md
View File

@ -173,6 +173,10 @@ In case of command line applications, an option must be provided (suggestion –
### Version Control and Repository Management
## Distributed Computing Specifications
The guides below aim to clarify principles and design decisions when creating distributed systems. Whether the software you are building is distributed or centralized, it is important to follow the points mentioned in this sections. This will make sure that any centralized software can later be transformed into a distributed system without much headache.
@ -192,7 +196,7 @@ All software at DIT is deployed using Docker and will be running on Kubernetes.
#### Dockerfile
The Dockerfile is a standard file that gives out instruction on how to build an image for the source code. Different technology stacks have different base images on the top of which the new image is built. DIT has a local registry for all needed images. The base images used in this Dockerfile must be coming from our local registry. If the on-prem registry does not contain the base images that you need, speak to the Head of DevOps so that they are made available. If it is absolutely necessary to use an image that for some reasons cannot be hosted on our local registry, speak to the Head of DevOps to obtain approval. Otherwise, the change is considered a bug.
The Dockerfile is a standard file that gives out instruction on how to build an image for the source code. Diffberent technology stacks have different base images on the top of which the new image is built. DIT has a local registry for all needed images. The base images used in this Dockerfile must be coming from our local registry. If the on-prem registry does not contain the base images that you need, speak to the Head of DevOps so that they are made available. If it is absolutely necessary to use an image that for some reasons cannot be hosted on our local registry, speak to the Head of DevOps to obtain approval. Otherwise, the change is considered a bug.
@ -237,6 +241,10 @@ We also recommend reading the official [Best practices for writing Dockerfiles](
## Software Architecture Design and Non-functional Requirements
## Software Applications Specifications