By configuring git to not verify SSL certificates inside the development
container we can get rid of errors like this one when running
`docker-compose up`:
```
[...]
frontend_1 | bower angular#~1.3.0 ECMDERR Failed to execute "git ls-remote --tags --heads git://github.com/angular/bower-angular.git", exit code of #128
frontend_1 |
frontend_1 | Additional error details:
frontend_1 | fatal: unable to access 'https://github.com/angular/bower-angular.git/': Problem with the SSL CA cert (path? access rights?)
[...]
```
Here's the documentation on the `http.sslVerify` taken from
(http://git-scm.com/docs/git-config):
```
http.sslVerify
Whether to verify the SSL certificate when fetching or pushing over HTTPS. Can
be overridden by the GIT_SSL_NO_VERIFY environment variable.
```
It is better to directly go into the `develop` folder and start `docker-compose` from there. Otherwise it might try to copy everything within the current directory into the docker build context.
