Welcome! You must be here because you're interested in DevOps. Don't worry, we'll get to that in a moment! First, let's briefly go over some details.

"1.0" can be referred to as "Chapter One," while "1.2" can be referred to as "Chapter One, Section Two."

This DevOps Bootcamp is used as an introduction to DevOps for Liatrio's apprentices. Therefore, there are deliverables at the end of each section and knowledge checks sprinkled throughout that help guide the apprentices' training. However, anyone can go through the DevOps Bootcamp. Feel free to ignore the deliverables, knowledge checks, etc. This bootcamp also assumes the bootcamper is using a Mac for the deliverables.

This bootcamp alone will by no means make anyone an expert on DevOps; that's where real, in-the-field experience engineering and shadowing come in. However, this bootcamp is a great start for anyone entering the world of DevOps! It is recommended that anyone going through this bootcamp have a mentor to fill in the gaps of information and answer questions, as well. Also, many of the exercises proposed in this bootcamp have no solution listed. This is because it is up to the bootcamper to come up with the solution on their own. So, if you're wondering where a solution to an exercise is - there is likely none; that's up to you!

1. Introduction to DevOps
2. GitHub
3. Virtual Machines and Containers
4. Cloud Computing
5. Development Practices
6. Release Management
7. Infrastructure and Configuration
8. Kubernetes

1. Share what you learn. Knowledge is best retained when you can teach it back yourself.
2. If you're participating in the bootcamp with others, lift them up instead of speeding past them.
3. Your learning should be in a demonstrable state at any given time.
4. Slow and steady wins the race. If you don't fully understand something, speak up for help and spend more time on it.
5. Be transparent in your progress.
6. Have fun!

"It's better to over communicate than to under communicate."

Deliverables

If you are an apprentice (or if you just want to add to your learning), here's a little insight on the deliverables the bootcamp will provide. At the end of each section, you will typically encounter a bulleted list of deliverables. They will usually be structured to get you thinking/reflecting/researching key points that the section covered.

Knowledge Checks

As mentioned before, you'll also find small knowledge checks sprinkled throughout the bootcamp. Don't worry, they aren't graded and scores aren't tracked, so there's zero pressure when it comes to them. That being said, they are very valuable for learning, so it would be wise to take the time to not only get the correct answers on them, but to really understand why those are the correct answers.

Here's a sample knowledge check to show you how they'll behave:

This bootcamp was adapted from an apprentice training program, and some mistakes may have slipped through the cracks. If you see any errors, outdated methods, or citation errors please submit a pull request.

Below are a number of ways to develop locally, choose whichever you are most comfortable with.

Install Docsify locally (in current directory)

1. Run npm install
2. Run npm start
3. Open http://localhost:3000

Install Docsify Globally in your system

1. Install docsify
2. Navigate to local library of onboarding
3. Run docsify serve .
4. Open http://localhost:3000

Use Docker to build and serve the content, but remember to rebuild the Docker image to review changes

1. Execute docker build . -t devops-bootcamp from the project's root directory to generate a container image
2. Run docker run -d -p 3000:3000 --name devops-bootcamp devops-bootcamp to run a detached Docker container
3. Open http://localhost:3000

1. Run docker compose up -d
2. Open http://localhost:3000
3. To stop the container, run docker compose down

• Images should be placed under the root img folder and referred to using HTML <img> tags
• H3 header (###) should be the default header within a page
• H2 header (##) will appear in the navigation as the page's table of contents
• To add a new section, add a new file to docs such as x.x-new-section.md, and then reference it in docs/_sidebar.md.

Contributors