// the find
LondheShubham153/Shell-Scripting-For-DevOps
A course-style set of 19 numbered Bash scripts, ordered from hello-world through variables, conditionals, loops, functions and error handling to a backup script that ends in cron. It is written for the Udaan Batch 11 cohort, so it suits someone working through it with the class, or anyone who wants a linear path rather than a reference.
- The order is deliberate. The README's six topics map onto the numbered scripts (conditionals at 07 to 09, loops at 10 to 12, functions at 13 to 15, error handling at 18), so a learner can see where they are and what comes next.
- The practice loop (read, run, break it on purpose, rewrite from scratch without looking) is the strongest part of the README. It pushes the learner to modify code, which most shell tutorials skip.
- The README sends beginners to the right debugging tools: `bash -x` for tracing, shellcheck for static checks, and `man bash` as the reference.
- It goes past toy examples into things people actually do on servers: user creation, package install, system details, a tar/gzip backup with cron, and AWS EC2 provisioning with polling. The sample logs in log-files/ give grep, awk and tail something to work on.
- The README says to run each script but does not warn that 06_install_package.sh and 16_create_user.sh change system state. A learner running them on a laptop could end up with an unexpected user or package install. A line about using a VM or container would cost nothing.
- The visible tree has no tests and no CI config, so nothing checks that the scripts pass shellcheck or behave as the README describes. For a course about error handling, that gap is noticeable.
- There are two parallel paths: practice-scripts/ for the course and day01/ to day03/ as 'reference + history'. The README does not explain how the day scripts relate to the numbered ones, and some of the topics overlap.
- The mini-projects (deploy_django_app.sh and create_ec2.sh) are linked as one-line entries. The README does not list prerequisites such as AWS credentials, a running Docker daemon, or the git remote the deploy script expects, so readers will hit those failures without warning.