Portus targets version 2 of the Docker registry API. It aims to act both as an authoritzation server and as a user interface for the next generation of the Docker registry.
Portus supports the concept of users and teams. Each user has its personal Docker namespace where she has read (aka docker pull) and write (aka docker push) access.
A team is a group of users that have read and write access to a certain namespace.
Portus implements the token based authentication system described by the new version of the Docker registry. This can be used to have full control over the images served by an instance of the Docker registry.
Portus provides quick access to all the images available on your private instance of Docker registry. User's privileges are taken into account to make sure private images (the ones requiring special rights also for docker pull) are not shown to unauthorized personnel.
Portus' knowledge of the images available on the private instance of a Docker registry is built using the notifications sent by the Docker registry itself.
If Portus is unreachable when a new image is being pushed to the Docker registry, Portus won't be aware of it. This issue is going to be solved by next versions of Portus.
First of all, make sure that you have a working development environment. You can easily do this with either Docker or Vagrant, as it's explained on the wiki.
Also, make sure to understand our contribution guidelines, as explained in this document.
Happy hacking!
Portus is licensed under the Apache License, Version 2.0. See LICENSE for the full license text.