Welcome to the official learning repository for Batch-13 by DevOps Shack.

This repository is designed to help you:

• Learn real-world, production-grade DevSecOps
• Build hands-on projects module by module
• Create public proof of work
• Grow your visibility by learning in public

This is not a notes repo. This is a task-driven, execution-first engineering repository.

• Each top-level folder represents a module
• Inside each module, you will:
  • Complete assigned tasks
  • Add your implementation
  • Document what you learned
• Your work becomes:
  • A GitHub portfolio
  • A LinkedIn learning trail
  • An interview discussion asset

batch-13-production-devsecops/
│
├── 01-linux-shell/
├── 02-git/
├── 03-build-tools/
├── 04-ci-cd/
├── 05-sonarqube/
├── 06-security-devsecops/
├── 07-nexus/
├── 08-docker/
├── 09-kubernetes/
├── 10-azure-devops/
├── 11-terraform/
├── 12-ansible/
├── 13-monitoring-observability/
├── 14-python-for-devops/
├── 15-mlops-ai/
├── 90-capstone-projects/
│
└── README.md

You must fork this repository to your own GitHub account.

Example:

aditya-batch13-devsecops
rahul-batch13-devsecops
priya-batch13-devsecops

This helps recruiters clearly identify your work.

Inside each module folder:

• Code / scripts
• Configuration files
• Screenshots (if required)
• A README.md explaining:
  • What you did
  • Why it is needed in real projects
  • What issues you faced
  • How you fixed them

Example

01-linux-shell/
└── aditya/
    ├── task-01-linux-basics.md
    ├── task-02-permissions.md
    └── README.md

Share Updates on Discord & Amplify on LinkedIn

Learning in isolation limits your growth. To increase visibility, consistency, and reach, every Batch-13 learner is expected to share progress updates inside the Discord community and amplify the same learning on LinkedIn.

After completing each task or module, you must:

After completing a task or module:

Post a short update in the Batch-13 Discord channel

Share:

• What task you completed
• What you struggled with
• Any blockers or doubts
• GitHub link (if pushed)

• What you learned
• What problem you solved
• What mistake you made
• How this is used in real production systems

Why this matters:

• You learn faster by explaining
• Others learn from your mistakes
• Mentors and peers can guide you
• Your consistency becomes visible
• Silent learners don’t get noticed. Visible learners do.

• Aditya Jaiswal
• DevOps Shack

Once you tag Aditya Jaiswal and DevOps Shack, I get notified. I personally review your task, your approach, and your GitHub repository based on the effort and clarity shown.

Note: Reviews are effort-based, not automatic. Quality > quantity.

Use hashtags such as:

#Batch13 #DevOps #DevSecOps #LearnInPublic
#Docker #Kubernetes #CI_CD #Cloud #devopsshack

Consistency matters more than perfection.

Day X – #Batch13

Today I worked on <topic> as part of Batch-13.

❌ Issue I faced:
✅ How I fixed it:
🧠 Key learning:
🎯 How this is used in real production:

GitHub: <your forked repo link>

Thanks Aditya Jaiswal & DevOps Shack

• ❌ No copy-paste repos

• ❌ No blind execution without understanding

• ❌ No private repos for Batch-13 work

• ✅ Explain in your own words

• ✅ Commit regularly

• ✅ Build honestly

If you complete this repository seriously:

• You won’t just learn tools
• You’ll understand real DevSecOps workflows
• You’ll build visible proof of work
• You’ll stand out in interviews without trying hard

Welcome to Batch-13. Build. Share. Grow. 🚀