Go to file
Mike Heijmans 74004794b5
add pull command to information
fixes #9

also added `REGISTRY_PUBLIC_URL` variable for display in this command and in the footer
2016-05-18 10:35:41 -07:00
app add pull command to information 2016-05-18 10:35:41 -07:00
public handle slashes in container name 2016-05-17 11:23:49 -07:00
screenshots Use react single page app for browsing registry 2016-05-15 10:41:16 -07:00
.gitignore Use react single page app for browsing registry 2016-05-15 10:41:16 -07:00
.ruby-gemset ..and so it begins 2015-08-17 09:52:45 -07:00
.ruby-version ..and so it begins 2015-08-17 09:52:45 -07:00
Dockerfile Use react single page app for browsing registry 2016-05-15 10:41:16 -07:00
Gemfile Use react single page app for browsing registry 2016-05-15 10:41:16 -07:00
Gemfile.lock Use react single page app for browsing registry 2016-05-15 10:41:16 -07:00
LICENSE.md use some twitter bootstrap action 2015-08-17 22:34:45 -07:00
Procfile ..and so it begins 2015-08-17 09:52:45 -07:00
README.md add pull command to information 2016-05-18 10:35:41 -07:00
Rakefile Use react single page app for browsing registry 2016-05-15 10:41:16 -07:00
VERSION Use react single page app for browsing registry 2016-05-15 10:41:16 -07:00
apiserver.rb Use react single page app for browsing registry 2016-05-15 10:41:16 -07:00
circle.yml fix circle test 2016-05-15 10:50:03 -07:00
config.ru ..and so it begins 2015-08-17 09:52:45 -07:00
docker-compose.yml cleanup and ready for basic use 2015-08-18 10:23:38 -07:00
package.json Use react single page app for browsing registry 2016-05-15 10:41:16 -07:00
server.rb add pull command to information 2016-05-18 10:35:41 -07:00
unicorn.rb ..and so it begins 2015-08-17 09:52:45 -07:00
webpack.config.js Use react single page app for browsing registry 2016-05-15 10:41:16 -07:00

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+

Circle CI

screenshots/demo.gif

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?

Available Environment Variables:

  • REGISTRY_HOST - the registry host to browse (default: localhost)
  • REGISTRY_PORT - the port of the registry host (default: 5000)
  • REGISTRY_PROTO - the protocol to use (ie: http or https) (default: https)
  • REGISTRY_SSL_VERIFY - should the certificate be verified if using SSL (default: true)
  • REGISTRY_PUBLIC_URL - optional url to use for displaying in pull command and footer (default: REGISTRY_HOST:REGISTRY_PORT)
  • USERNAME - setting this will activate BASIC AUTH and require this username
  • PASSWORD - optional password for BASIC AUTH (you must set the USERNAME for this to work)
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 \
  -e USERNAME=admin \
  -e PASSWORD=s3cr3t \
  parabuzzle/craneoperator:latest

screenshots/Crane_Operator.jpg