π Intro Had a productive day focusing on Linux automation and Cloud fundamentals. Here is a quick log of what I learned and the commands I practiced today.
π 1. Crontab (Cron Table)
I finally sat down to master the syntax for scheduling jobs in Linux. The Syntax: * * * * * command_to_execute
Minute (0-59)
Hour (0-23)
Day of Month (1-31)
Month (1-12)
Day of Week (0-6)
What I practiced: Running a backup script every day at 5 AM:
Bash
0 5 * * * /home/user/scripts/backup.sh
Pro-tip: Always use absolute paths in cron jobs!
π 2. Bash Scripting: The jq Command
I realized that if you are working with AWS CLI or APIs in Bash, you need jq. Itβs a lightweight and flexible command-line JSON processor.
The "Aha" Moment: Instead of grepping through JSON output, I can parse it cleanly.
Bash
Before (Messy)
curl https://api.example.com/data
After (Clean)
curl https://api.example.com/data | jq '.'
I also learned how to extract specific values to store in variables:
Bash
VERSION=$(cat package.json | jq -r '.version')
π² 3. Git Refresher
Revised the essentials to ensure my workflow is solid.
git status: Checking the state of the working directory.
git log --oneline: A cleaner way to view commit history.
git diff: Seeing exactly what changed before staging.
βοΈ 4. AWS Services for DevOps
I mapped out the AWS services that are non-negotiable for a DevOps role. This isn't just "knowing" them, but understanding how they integrate:
VPC: Networking is the foundation.
EC2 & Auto Scaling: For managing compute loads.
S3: For artifact storage and state files.
IAM: Security and permissions (Principles of Least Privilege).
RDS/DynamoDB: Database management.
Route53: DNS management.
π Wrap Up
The combination of Bash scripting (crontab/jq) and Cloud knowledge is powerful.
Top comments (0)