ef1030878b
* remove focus box on buttons in chrome * add proptype contstraints to components |
||
|---|---|---|
| app | ||
| public | ||
| screenshots | ||
| .gitignore | ||
| .ruby-gemset | ||
| .ruby-version | ||
| Dockerfile | ||
| Gemfile | ||
| Gemfile.lock | ||
| LICENSE.md | ||
| Procfile | ||
| README.md | ||
| Rakefile | ||
| VERSION | ||
| apiserver.rb | ||
| circle.yml | ||
| config.ru | ||
| docker-compose.yml | ||
| package.json | ||
| server.rb | ||
| unicorn.rb | ||
| webpack.config.js | ||
README.md
CraneOperator
Just as crane operators can see where all the containers that are in the shipyard, CraneOp gives you a simple web interface for browsing around a Docker Registry running version 2.0+
Why Crane Operator?
When you run your own internal docker registry, it can be challenging to find out what has been saved there. I wanted to create a simple and lightweight frontend for browsing my registry. Most solutions that exist are built for registry v1 and don't work with the newer registry v2. (to be honest, its hard enough to even get registry v2 working... browsing it shouldn't be)
How do I run it?
docker run -d -p 80:80 parabuzzle/craneoperator:latest
How do I configure it?
docker run -d \
-p 80:80 \
-e REGISTRY_HOST=registry.yourdomain.com \
-e REGISTRY_PORT=443 \
-e REGISTRY_PROTO=https \
-e REGISTRY_SSL_VERIFY=false \
parabuzzle/craneoperator:latest
