Author: pforret

BashPitfalls
This page is a compilation of common mistakes made by bash users. Each example is flawed in some way. Yes, it would be great if you could just treat the output of ls or find as a list of filenames and iterate over it. But you cannot.
—
https://mywiki.wooledge.org/BashPitfalls

Bash With Nails
Bash With Nails (rhymes with ruby on rails) is a bash framework written for fun and profit. I’m kidding about the fun and profit part.
—
https://github.com/mindaugasbarysas/bashwithnails

Learn
Nix is a package manager which comes in a form of many command line tools. Packages that Nix can build are defined with the Nix Expression Language.
—
https://nixos.org/learn.html

cheat cheat allows you to create and view interactive cheatsheets on the command-line. It was designed to help remind *nix system administrators of options for commands that they use frequently, but not frequently enough to remember. Use cheat with cheatsheets.
—
https://github.com/cheat/cheat

The command line is something every developer should learn and implement into their daily routine. It has become a Swiss Army knife of features behind deceptively simple commands, which allow you to gain greater control of your system, become more productive, and much more.
—
https://www.educative.io/blog/bash-shell-command-cheat-sheet

I created it because I wanted a very, very simple way to post entries to a blog by using a public folder on my server, without any special requirements and dependencies. Works on GNU/Linux, OSX and BSD. How simple? Just type ./bb.sh post and start writing your blogpost.
—
https://github.com/cfenollosa/bashblog

Back when I started writing code, everything was done in the command line. You configured systems with the command line, wrote scripts in vi and emacs and ed, building your own library of commands that simplified your tasks and automated the complex.

To make it easier for users and contributors to see precisely what notable changes have been made between each release (or version) of the project. People do. Whether consumers or developers, the end users of software are human beings who care about what’s in the software.

https://keepachangelog.com/en/1.0.0/

This is beta quality! Use at your own risk. Use a yaml file to stitch together commands and bash snippets and run them with a bit of style. Why? Because your bash script should be quiet and shy-like (…and not such a loud mouth).

https://github.com/wagoodman/bashful