$PATH and .bashrc File in Shared Server

Installing Git or doing SSH on a shared hosting account is simple and in most cases go without documentation. Here is some words on $PATH and and .bashrc File in Shared Server. For the most users, who has an average knowledge about environmental variable – they will need top up knowledge on $PATH, like we described on $PATH Variable Guide for OS X. We have discussed how to SSH in Shared Hosting Server, using Git Repo In Shared Hosting. In this context, it is important to know something about VirtFS or Jailed Shell.

 

$PATH and .bashrc File in Shared Server

 

We usually start with a bare repository. All other repositories are cloned from this one. Master is usually a standard repository, the live web site from the Push is served from the working directory. Using a pair of repositories is simple and flexible way of managing stuffs on a Multi-tenant environment where Git is the files for the working live website. Remote clones with ssh-access can update a live site with a simple git push to the main first repository. Any files edited directly on the server are instantly mirrored into the first repository upon commit. Git is a priority above all of the other tools used today. Git really changed the way developers think of merging and branching.

But none of these advanced ideas will work if we do not update the $PATH environment variable. In most cases, this is set in the .bashrc file. Using a .bashrc file instead of a .bash_profile updates the $PATH for interactive and non-interactive sessions“which is necessary in many cases. We can simply add these two lines on .bashrc file :

 

Do More With New $PATH and .bashrc File Changes on Shared Server

 

We should source the file and echo to double check :

Previous methods used to install the stuffs into the ~/opt directory. We will now be installing stuffs into the default ~/bin. You must have the permission to use GCC on the server. Run the following command to check :

On OS X, we will get output like this :

If we get output like /usr/bin/gcc: Permission denied simply we do not have the access to the GCC compiler and we will not be able to build the Git binaries from source. We can simply run :

In this case, we are running a Git server. If the GCC compiler throws error, you will be unable to use this method.