You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p>I don't know how you stumbled upon my corner of the internet, but I'm glad you're here.</p>
17
-
<h2>Brief Intro</h2>
18
-
<p>Welcome to my little slice of cyberspace! G-yan isn't my official name, but some friends call me that—long story short, it stuck. I'm a DevOps engineer with an insatiable passion for cutting-edge technologies. I'm in the process of creating this website where I'll study, research, and document all things tech, and then host it on GitHub Pages.</p>
19
-
<p>This site is designed to be a treasure trove of knowledge for System Administrators, DevOps aficionados, and SRE professionals. If you’ve accidentally landed here, sit tight. You're in for a ride filled with tech insights, a dash of humor, and perhaps a few surprises. Buckle up and enjoy! Lol!</p>
20
-
<h2>Tech Humor Corner</h2>
21
-
<p>While you're here, why not enjoy a few tech-themed jokes? After all, even code needs a bit of fun!</p>
22
-
<pre>$touch<br>Ever feel like you need to create a new file in your life? Just use touch—no strings attached!</pre>
23
-
<pre>$top<br> When people ask me how I manage to stay so productive, I just tell them I’m always on top.</pre>
24
-
<pre>$finger<br>Don’t worry, it’s not what you think. Just a friendly way to find out more about someone in Unix.</pre>
25
-
<pre>$sleep<br>If only I could sleep 8 hours every night—life would be so much easier.</pre>
26
-
<pre>$date<br>Why go on Tinder when you can simply type date and get one instantly?</pre>
27
-
<pre>$kill<br>Sometimes, you just need to kill those bad processes—no crime shows required.</pre>
28
-
<pre>$man<br>Looking for guidance? Just ask the man. He’s got all the answers.</pre>
29
-
<p>So, whether you're here for the laughs, the learning, or a little bit of both, welcome! Feel free to explore, and don’t hesitate to reach out if you have questions or just want to share a joke of your own.</p>
<p>Welcome to DevOpsHub! Designed especially for those with some experience in the IT industry. Whether you are transitioning or planning to transition to a DevOps career from various backgrounds such as System Administration, Software Development, QA & Test Automation, or Network Engineering, this platform is tailored to support your journey.</p>
3
+
<p> </p>
4
+
<p>Here, you will find real-time work references that can assist you with your daily tasks, job searches, and practice routines. We emphasize the importance of testing before implementing any online content into your real-time projects. For more details, please refer to our policy page.</p>
5
+
<p> </p>
6
+
<p>Our website is an open-source project, allowing anyone to contribute via GitHub. If you're interested in content creation, we provide a content hierarchy for your reference. You are welcome to add new titles and pages as needed, which will be reviewed for potential inclusion.</p>
7
+
<p> </p>
8
+
<p>We cover a range of topics including DevOps introduction, CI/CD pipelines, tools, and roadmaps. Join us in building a comprehensive resource for IT professionals and DevOps enthusiasts.</p>
Copy file name to clipboardexpand all lines: docs/pages/devops_intro.html
+11-11
Original file line number
Diff line number
Diff line change
@@ -13,9 +13,9 @@
13
13
<p> </p>
14
14
<p>DevOps covers the whole software development lifecycle, so you work with lots of different tools and technologies. Plus, DevOps is still evolving and there are lots of new tools being developed all the time.</p>
<h3><spanstyle="color:#1565c0;"><strong>1. Concepts of Software Development</strong></span></h3>
18
+
<h3><spanstyle="color:#15ff00;"><strong>1. Concepts of Software Development</strong></span></h3>
19
19
<p>As a DevOps engineer you will not be programming the application, but as you are working closely with the development team to improve and automate tasks for them, you need to understand the concepts of:</p>
20
20
<ul>
21
21
<li>How developers work and collaborate (Agile, Jira workflows)</li>
@@ -25,7 +25,7 @@ <h3><span style="color:#1565c0;"><strong>1. Concepts of Software Development</st
25
25
</ul>
26
26
<p>And generally understand what the whole software development lifecycle covers from idea to code, all the way to releasing it to end users.</p>
27
27
<p> </p>
28
-
<h3><spanstyle="color:#1565c0;">2. OS & Linux Basics</span></h3>
28
+
<h3><spanstyle="color:#15ff00;">2. OS & Linux Basics</span></h3>
29
29
<p>As a DevOps engineer you are responsible for preparing and maintaining the infrastructure (servers) on which the application is deployed. So you need to know the basics of how to administer a server and install different tools on it.</p>
30
30
<p>Since most servers use Linux OS, you need to know and feel comfortable using Linux, especially its Command Line Interface. Basic concepts of Operating Systems you need to understand:</p>
31
31
<ul>
@@ -43,7 +43,7 @@ <h3><span style="color:#1565c0;">2. OS & Linux Basics</span></h3>
<p>Docker is by far the most popular container technology.</p>
48
48
<p>As containers have become the new standard of software packaging, you will most probably run your application as a container. This means you need to generally understand:</p>
<p>CI/CD is kind of the heart of DevOps. In DevOps, all code changes, like new features or bug fixes, need to be integrated into the existing application and deployed to the end users continuously and in an automated way. Hence, the term: Continuous Integration and Continuous Deployment (CI/CD).</p>
67
67
<p>When the feature or bug-fix is done, a pipeline running on a CI server (e.g. Jenkins) should be triggered automatically, which:</p>
<li>Configuring artifact repositories (like Nexus) and integrate with pipeline</li>
83
83
</ul>
84
84
<p> </p>
85
-
<h3><spanstyle="color:#1565c0;">5. Learn One Cloud Provider - AWS</span></h3>
85
+
<h3><spanstyle="color:#15ff00;">5. Learn One Cloud Provider - AWS</span></h3>
86
86
<p>Some popular Cloud platforms are - AWS, Microsoft Azure, Google Cloud. AWS is the most powerful and most widely used IaaS platform, but also a difficult one.</p>
87
87
<p>Nowadays, many companies use virtual infrastructure on the cloud, instead of managing their own infrastructure. These are Infrastructure as a Service (IaaS) platforms, which offer a range of additional services, like backup, security, load balancing etc.</p>
<p>Since containers are popular and easy to use, many companies are running hundreds or thousands of containers on multiple servers. This means these containers need to be managed somehow. For this purpose, there are container orchestration tools.</p>
99
99
<p>Kubernetes (also known as K8s) is the most popular container orchestration tool. Kubernetes automates the deployment, scaling and management of containerized applications.</p>
<h3><spanstyle="color:#1565c0;">7. Monitoring & Observability - Prometheus & Grafana</span></h3>
113
+
<h3><spanstyle="color:#15ff00;">7. Monitoring & Observability - Prometheus & Grafana</span></h3>
114
114
<p>Once software is in production, it is important to monitor it to track the performance, discover problems in your infrastructure and the application.</p>
115
115
<p>So one of your responsibilities as a DevOps engineer is to:</p>
<p>You should also understand how systems can collect and aggregate data with the goal of using it to troubleshoot, gain business insights etc.</p>
125
125
<p><strong>ELK Stack:</strong> A popular log management stack.</p>
126
126
<p> </p>
127
-
<h3><spanstyle="color:#1565c0;">8. Infrastructure as Code - Ansible & Terraform</span></h3>
127
+
<h3><spanstyle="color:#15ff00;">8. Infrastructure as Code - Ansible & Terraform</span></h3>
128
128
<p>Manually creating and maintaining infrastructure is time consuming and error prone. Especially when you need to replicate the infrastructure, e.g. for a Development, Testing and Production environment.</p>
129
129
<p>In DevOps, we want to automate as much as possible and that's where Infrastructure as Code comes into the picture.</p>
130
130
<p>With IaC we use code to create and configure infrastructure and there are 2 types of IaC tools you need to know:</p>
@@ -136,14 +136,14 @@ <h3><span style="color:#1565c0;">8. Infrastructure as Code - Ansible & Terra
136
136
<p><strong>Terraform:</strong> This is the most popular infrastructure provisioning tool.</p>
137
137
<p><strong>Ansible: </strong>This is the most popular configuration management tool.</p>
138
138
<p> </p>
139
-
<h3><spanstyle="color:#1565c0;">9. Scripting Language - Python</span></h3>
139
+
<h3><spanstyle="color:#15ff00;">9. Scripting Language - Python</span></h3>
140
140
<p>Since you are closely working with developers and system administrators to also automate tasks for development and operations, you will need to write scripts and small applications to automate them. For that, you will need some scripting or basic programming skills.</p>
141
141
<p>Examples: utility scripts like flushing the cache, starting the builds and deployments etc.</p>
142
142
<p>This could be an OS specific scripting language like bash or Powershell. But what's more demanded is an OS-independent language like Python, Ruby or Go.</p>
143
143
<p>These languages are more powerful and flexible. If you know one of these, it will make you much more valuable as a DevOps engineer.</p>
144
144
<p>There are many programming languages, but I would recommend starting with Python. Python is widely used, easy to learn and used in many different cases, especially in DevOps.</p>
145
145
<p> </p>
146
-
<h3><spanstyle="color:#1565c0;">10. Version Control - Git</span></h3>
146
+
<h3><spanstyle="color:#15ff00;">10. Version Control - Git</span></h3>
147
147
<p>You write all automation logic as code. And just application code, automation code should also be managed and hosted on a version control tool, like Git.</p>
148
148
<p>Git is a CLI Tool, which you install locally. It enables the tracking of changes in the source code and enables better collaboration on code.</p>
<p>The commands and content provided on this website are intended for informational and educational purposes only. While we strive to ensure the accuracy and reliability of the information presented, we cannot guarantee that it will be suitable for all environments or configurations.</p>
18
-
<h2>Important Notice</h2>
19
-
<p>1. Use at Your Own Risk: The commands and scripts shared here are for your knowledge and information. Before executing any commands or scripts, it is crucial that you test them in a controlled environment. The behavior of commands can vary depending on your system configuration, platform, and other factors.</p>
20
-
<p>2. Testing: Always test commands and scripts in a safe, non-production environment first to ensure they work as expected without causing unintended consequences.</p>
21
-
<p>3. Responsibility: You are solely responsible for any actions you take based on the information provided on this website. We are not liable for any damages, losses, or issues that may arise from the use or misuse of the content available here.</p>
22
-
<p>4. Updates and Changes: We may update or change the content on this website at any time without notice. It is your responsibility to stay informed about any changes that may affect your use of the information provided.</p>
23
-
<p>By using this website, you acknowledge that you have read and understood this policy and agree to use the information provided responsibly and at your own risk.</p>
24
-
<p>Thank you for visiting, and happy learning!</p>
<p>The commands and content provided on this website are intended for informational and educational purposes only. While we strive to ensure the accuracy and reliability of the information presented, we cannot guarantee that it will be suitable for all environments or configurations.</p>
<p>1. Use at Your Own Risk: The commands and scripts shared here are for your knowledge and information. Before executing any commands or scripts, it is crucial that you test them in a controlled environment. The behavior of commands can vary depending on your system configuration, platform, and other factors.</p>
6
+
<p>2. Testing: Always test commands and scripts in a safe, non-production environment first to ensure they work as expected without causing unintended consequences.</p>
7
+
<p>3. Responsibility: You are solely responsible for any actions you take based on the information provided on this website. We are not liable for any damages, losses, or issues that may arise from the use or misuse of the content available here.</p>
8
+
<p>4. Updates and Changes: We may update or change the content on this website at any time without notice. It is your responsibility to stay informed about any changes that may affect your use of the information provided.</p>
9
+
<p>By using this website, you acknowledge that you have read and understood this policy and agree to use the information provided responsibly and at your own risk.</p>
10
+
<p>Thank you for visiting, and happy learning!</p>
0 commit comments