Search Results for "reason"

This repository is used to document my journey on getting a better foundational knowledge of DevOps. I will be starting this journey on the 1st January 2022 but the idea is that we take 90 days which just so happens to be January 1st to March 31st. The reason for documenting these days is so that others can take something from it and also hopefully enhance the resources. The goal is to take 90 days, 1 hour a day, to tackle over 13 areas of DevOps to foundational knowledge. This will not cover all things DevOps but it will cover the areas that I feel will benefit my learning and understanding overall. ...

...The files should be placed in .git/hooks In the directory hooks you can find examples of all the hooks available. You can easily publish a feature you are working on. The reason can be to allow other programmers to work on it or to access it from another machine.

...With bocker you can perform basic operations such as pulling an image, running a container, exec into a container, listing containers, and removing them. Because it's written in shell, it is easy to read, reason about, and adapt for experiments or instructional use. It is not intended for production use due to performance, security, and missing features, but it is a useful tool for learning how containers work under the hood. Many learners and educators reference it when teaching container internals or when debugging container behavior in a minimal environment.

The Orchestrator server is responsible for distribution and launch of simple apply/rollback shell scripts in a particular order across multiple servers . If for any reason deployment is failing at a particular stage the process will stop and you can rollback any changes done until then. In case you want to deploy your code or just call your preferred DSC client to apply the configuration locally the Orchestrator can be a handy tool. The operation can be started manually or scheduled, depending on your needs. ...