Welcome To Our Shell

Mister Spy & Souheyl Bypass Shell

#Permissions
You may receive an **EACCESS** error when you try to install a package globally. This indicates
that you do not have permission to write to the directories that npm uses to store global
packages and commands.

There are two options to fix this problem:
1. Change the permissions to npm's default directory
2. Change npm's default directory to another directory

Both these options are fully supported by the DevOps team. If you have chosen a different
path, please be warned that we can give you only reduced support on your specific
problems.

##Option 1
1. Find the path to npm's directory:
```
npm config get prefix
```

> **WARNING!** If your path is /usr, switch immediately to option 2

2. Change the over of npm's directory's to the current user:

```
sudo chown -R `whoami` <directory>
```

If you don't want to change the permissions on the entire directory, you can change
the permissions of the subfolders **lib/node_modules, bin and share**.

##Option 2
If you pick option 2 for you, you need to configure npm to use a different directory.

1. Make a directory for global installations:
```
mkdir ~/devops-npm-global
```

2. Configure npm to use the new directory path:
```
npm config set prefix '~/devops-npm-global'
```

3. Open or create a ~/.prfile file and add this line:
```
export PATH=~/devops-npm-global/bin:$PATH
```

4. Back on the command line, update your system variables:
```
source ~/.profile
```

From now on, you are able to install packages globally without using sudo and without
having changed the permissions on /usr/local