jq is like sed for JSON data – you can use it to slice and filter and map and transform structured data with the same ease that sed, awk, grep and friends let you play with text.
jq is written in portable C, and it has zero runtime dependencies. You can download a single binary, scp it to a far away machine, and expect it to work.
jq can mangle the data format that you have into the one that you want with very little effort, and the program to do so is often shorter and simpler than you’d expect.
The hub subcommand for git, allows you to perform many of the operations made available by GitHub's v3 REST API, from the git commandline command.
You can fork, create, delete and modify repositories. You can get information about users, repositories and issues. You can star, watch and follow things, and find out who else is doing the same. The API is quite extensive. With this command you can do many of your day to day GitHub actions without needing a web browser.
Facy is a terminal client for facebook, which support streaming-like feature. Only supports Ruby 1.9 and later. To install facy, we need ruby pre-installed, please refer to https://www.ruby-lang.org/en/installation/ to know how to install ruby. I recommend rvm to control the version of installed ruby.
A smart and nice Twitter client on terminal wrote by Python.
You just replace use Getopt::Long with use Getopt::Long::Complete and your program suddenly supports tab completion. This works for most/many programs.
The TTY subsystem is central to the design of Linux, and UNIX in general. Unfortunately, its importance is often overlooked, and it is difficult to find good introductory articles about it. I believe that a basic understanding of TTYs in Linux is essential for the developer and the advanced user. Beware, though: What you are about to see is not particularly elegant. In fact, the TTY subsystem — while quite functional from a user's point of view — is a twisty little mess of special cases. To understand how this came to be, we have to go back in time.
lc-tools is a set of command line tools to control various clouds. It uses libcloud for cloud related stuff so should support as much cloud providers as libcloud does.
Dewpoint is a command line tool for interacting with cloud servers.
Usage: dewpoint [options] ...
create-node Create a new node
destroy-node Destroy an existing node
find-node Find an existing node by name
list-nodes List all existing nodes
list-sizes List all valid server sizes
list-images List all available server images
help Return more detailed help on command
I was going to write something like this myself (for an experimental fully automated continuous deployment pipeline using only open-source tools) but this looks promising so maybe I won't have to.
Here are a couple of quick tips for writing more robust shell scripts from my last 10 years of working with bash.
▁▂▃▅▂▇ in your shell.