*nix Aliases We all know how aliases on the *nix system help to create short commands for the long ones. E.g. can stand for or for . Software associates create such aliases and write them in the file. So aliases are available whenever they logged in to their machine. kga kubectl get all gl git log --name-status --decorate ~/.bashrc The Challenge However, associates also need to log in to other *nix machines for various purposes. Say a developer needs to log in to the SV system for live troubleshooting of an issue. Or a DevOps Engineer requires to log in to various cloud VMs. One has become very used to his/her alias s/he has created. It's very difficult to copy/paste the aliases every time s/he logs in to the another machine. The Solution Here is one way to address this challenge. Create your aliases, categorize and put them in different files. Say , , etc. Then create a file. Download it on the machine you have logged in. General Aliases Git Aliases Docker Aliases setaliases.sh wget https://raw.githubusercontent.com/simplyatul/bin/master/setaliases.sh and then source it source setaliases.sh That's it. All your aliases are set. If you are frequently logging in to a particular machine, then just copy the above source command in the file. ~/.bashrc Also published . here

The code in this story is for educational purposes. The readers are solely responsible for whatever they build with it.

Read My Stories

Too Long; Didn't Read

In your car, at home, or at work — Bosch technology shapes many areas of life.

Bash Aliases: Take Them With You

Too Long; Didn't Read

Atul Thosar

STORY’S CREDIBILITY

Code License

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

Bash Aliases: Take Them With You

Too Long; Didn't Read

Atul Thosar

STORY’S CREDIBILITY

Code License

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

RELATED STORIES