a BASH script PUSH-UP counter (for #gains )

A bash push-up counter built with loops turns basic scripting into something immediately useful: it repeatedly prompts, counts, and stops based on simple conditions. Starting from a “while” loop that increments a counter until a limit is reached, the script demonstrates how bash can automate repetitive tasks—then quickly pivots to a more interactive version that asks for user input (press Enter to continue) and lets the user choose how many push-ups to do. The practical takeaway is that loops aren’t just programming exercises; they’re a way to control repetition, pacing, and termination in real workflows.

The lesson then broadens from “while” to “until,” framing “until” as the upside-down counterpart: “while condition is true, keep looping” versus “until condition becomes true, keep looping.” A coffee-or-tea example makes the difference concrete. The loop keeps asking for input until the user types “coffee,” at which point the condition flips and the script ends. That same pattern—looping until a goal state is reached—reappears later in a network-check scenario.

Next comes the “for” loop, introduced as the tool for iterating over a known list of values. A simple cups-of-coffee example shows how a loop variable takes on each item in a sequence (1 through 10), and the script runs once per item. The transcript also highlights a shorthand range syntax using braces (e.g., {1..10}), which makes loops easier to read and maintain.

The most “real-world” uses arrive with two for-loop examples. One script iterates over a list of domains, pings each one quietly, and uses an if/else check to print whether each site is up or down. Another script reads city names from a text file and uses curl to fetch current weather for each city, echoing results directly in the terminal. Together, these examples show how loops combine with command-line tools to batch-check connectivity and automate data retrieval.

Because loops can run forever, the transcript spends time on safety controls. A “while true” example is intentionally dangerous—then stopped with Ctrl+C—before introducing “break” as the clean escape hatch. A connectivity monitor loop uses “break” to exit as soon as a ping succeeds, avoiding endless repetition. Finally, “continue” is demonstrated in an “elevator” style loop: when the loop variable hits 13, the script skips that iteration and moves on, producing a sequence that omits a specific value.

By the end, the core message is that bash’s while, until, and for loops—plus break and continue—form a small set of building blocks that unlock automation. Whether counting reps, validating user input, checking servers, or pulling weather for many cities, the same control-flow patterns keep repetition predictable and stop conditions under control.