Dive into Docker takes you from "What is Docker?" to confidently applying Docker to your own projects. It's packed with best practices and examples. Start Learning Docker →
This could be handy to see how many people committed to a repo or find out who the recent contributers are.
It will add a new line by default which will change your value, consider using printf instead or at least echo with the -n flag.
This can be really handy if you want to do something specific in a shell script only if a file has been changed in git.
We'll go over creating the logic for the whitelist, an optional exempt list, working with CIDR blocks and benchmarking a few solutions.
Cut can make quick work out of extracting useful data from CSV files or output that has a pattern of characters or bytes.
With 1 line of code and 1 function we'll be able to randomly pick something X% of the time and something else Y% of the time.
This will work if you're using bash or zsh and it doesn't require installing any third party tools or plugins.
It compares uncommitted changes vs your latest commmit, --cached does the same thing, it's an alias to --staged.
Sometimes you may want to back out of the latest Docker Desktop and install an older version. Here's how to do that.
This is handy in case you forgot to copy something or decide you want to select a few more lines.
Redis has 2 commands to help you discover how fast or slow it is to connect to your Redis server and how good your Redis server is.
As of May 30th 2022 Google disabled the less secure apps option to login to Gmail over SMTP, 2FA + app passwords fill that void.
This is handy to prevent typos because this option will halt your script as soon as an unset variable is found.
This is really handy to avoid having to add a source path as a comment or ignore SC1091 every time you source a file.
You can use this workflow to help convert feature requests, user stories and vague ideas into fully working code.
If I'm trying to research something or solve a specific problem I typically reach for the same resources with different search terms.
Even if you're using a Bash shebang you can run ShellCheck with the --shell flag to supply a different shell to check against.
This could be useful to locally rewrite history before pushing your changes up or before making a pull request.
Even if you plan to use set -e it feels like a reasonable idea to add this to most cd commands you use in a script.
Here's a recap of a few things that went wrong around pushing invalid Python packages while maintaining Flask-DebugToolbar.
Like you, I'm super protective of my inbox, so don't worry about getting spammed. You can expect a few emails per month (at most), and you can 1-click unsubscribe at any time. See what else you'll get too.