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.
Somehow grunt-wiredep kicks out bootstrap from the app/index.html file.
This is not nice and we need to find a better way than to simply commen
it out in the build step but for now it fixes the issue of missing
Bootstrap CSS.
I did some cleanup and unified the deletion of items (e.g. tags or repos) a bit.
Now, you can select multiple repositories or tags and delete them at once.
Confirmation is done using a modal popup.
Success and error messages will still be prompted for each operation using
toastr notification.
One thing that is still missing is the selection of multiple items using some
automation like a stupid "select all" button.
Also, any selected item remains selected even if it does not show up any longer
due to filtering. That's why the delete buttons explicitly tell the number of
items to be deleted. This can cause issues when paging (not implemented yet) or
filtering.
* moimael-master:
Re-added glyphicons and git revision in footer
Update bootstrap and angular-bootstrap
Make footer smaller and always sticked to bottom of the window
Update grunt-connect-proxy to 0.2.0
When the container is started for the first time we save a copy of the original `/etc/apache2/envvars` file to `/etc/apache2/envvars.orig`. On a container restart we copy the original file `/etc/apache2/envvars.orig` to `/etc/apache2/envvars` and modify it as usual without appending settings to `/etc/apache2/envvars` over and over.
Before starting Apache in the foreground we ensure that it is not running by explicitly stopping the service.
With this change, no destructive requests (e.g. PUT, POST, DELETE) are allowed
on the frontend site which proxies through to the actual registry. This should
make the browse only mode more safe.
See PR #15
