Skip to content
Helpful bash aliases for true professionals.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
bash Add yarn aliases (#89) Jan 16, 2019
doc
README.md
bash_aliases
git_aliases

README.md

.aliases

If you use the terminal on a daily basis, you'll eventually find yourself wanting aliases for your most commonly-used commands. It's incredibly useful to be able to execute your commands with only a few keystrokes that ultimately get hardcoded into muscle memory.

This repository is an easy to install project that contains a growing list of aliases for different frameworks and tools that works on any *nix system.

The project was started with passion by the Algotech Software Engineering Team.

Aliases list

Bash aliases

Tools:

PHP:

JavaScript:

  • Npm aliases - package manager for the JavaScript programming language
  • Yarn aliases - package manager for the JavaScript programming language
  • Gulp aliases - toolkit for automating painful or time-consuming tasks
  • Loopback aliases - highly-extensible, open-source Node.js framework
  • Cordova aliases - cross-platform mobile application development

Python:

Ruby:

Git aliases:

  • You can find the documentation for git aliases here. Those are different than the above described bash aliases.

Installation

Clone it into .aliases folder in your home directory:

cd ~
git clone https://github.com/algotech/dotaliases.git .aliases

Enable bash aliases for new terminals: add to ~/.bash_profile or ~/.profile

source ~/.aliases/bash_aliases

Enable bash aliases in the current opened terminal by running the command:

source ~/.aliases/bash_aliases

Using with vagrant

  • clone the repository to a folder of your choice
  • copy .aliases to vagrant shared folders (do not forget to add it to .gitignore as well)
  • edit bash_aliases and replace the line ALIASES_HOME=$HOME with your path in vagrant, e.g. ALIASES_HOME='/vagrant'
  • source bash_aliases from its location whenever you ssh into the vagrant box
You can’t perform that action at this time.