# Can you do all of these without searching?
mkdir -p ~/devops-practice/logs && cd ~/devops-practice
echo "hello" > notes.txt
ls -la
chmod 600 notes.txt
ps aux | grep ssh
df -h
curl -I https://example.com
# If 6 or more feel easy, your Linux basics are ready.

git init -b main demo && cd demo
echo "# Demo" > README.md
git add README.md
git commit -m "Add README"
git checkout -b feature/notes
echo "note" > notes.md
git add notes.md && git commit -m "Add notes"
git checkout main
git merge feature/notes
git log --oneline

Ask in the demo class:
1. Will I have my own lab machine or cloud account?
2. How many hours per week are hands-on?
3. What happens when my Docker build fails in class?
4. Is there one project that connects all tools?
5. Which CI tool and which cloud do you use?
6. How are doubts handled between classes?

End-to-end DevOps project (what to look for)
- App code in Git with branches and pull requests
- Dockerfile and image pushed to a registry
- CI pipeline: build, test, scan, push
- CD: deploy to Kubernetes or a cloud service
- Infrastructure created with Terraform
- Monitoring dashboard and one alert
- README with architecture diagram

Weekly hours check
Work/college hours:      ____
Class hours:             ____
Travel for class:        ____
Lab practice needed:     at least equal to class hours
Free hours left:         ____
If free hours < practice needed → choose online or weekend batch

Fee and Support Record
Institute: ____________
Total fee (with tax): ________
Instalments: yes / no
Recordings: yes / no
Batch repeat: yes / no
Doubt support: how ______
Career support: resume / mock interviews / scheduling
All of the above in writing? ☐

DevOps Class Scorecard (1-5)
                      Class A   Class B   Class C
Lab setup               ___       ___       ___
Trainer troubleshooting ___       ___       ___
Syllabus order          ___       ___       ___
End-to-end project      ___       ___       ___
Batch timing            ___       ___       ___
Travel / online option  ___       ___       ___
Support in writing      ___       ___       ___
TOTAL                   ___       ___       ___

Two-week pre-joining plan
Week 1: Linux commands, files, permissions, processes, SSH
Week 2: Git basics, branches, GitHub; one Bash script
Daily: 45-60 minutes
Outcome: pass the Linux and Git self-tests

First month goals after joining
☐ Comfortable on the Linux server used in labs
☐ Docker image built for a sample app
☐ First CI pipeline running on push
☐ Notes and code pushed to GitHub weekly