vbatts/registry
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Rename top level registry interface to namespace

Browse source 
Registry is intended to be used as a repository service than an abstract collection of repositories. Namespace better describes a collection of repositories retrievable by name.
The registry service serves any repository in the global scope.

Signed-off-by: Derek McGowan <derek@mcgstyle.net> (github: dmcgowan)
This commit is contained in:
Derek McGowan 2015-04-09 19:21:33 -07:00
parent 5dd885b311
commit 142d62798e
7 changed files with 47 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/configuration.md
View file

@ -283,7 +283,7 @@ For more information about Token based authentication configuration, see the [sp
## middleware
The middleware option is **optional** and allows middlewares to be injected at named hook points. A requirement of all middlewares is that they implement the same interface as the object they're wrapping. This means a registry middleware must implement the `distribution.Registry` interface, repository middleware must implement `distribution.Respository`, and storage middleware must implement `driver.StorageDriver`.
The middleware option is **optional** and allows middlewares to be injected at named hook points. A requirement of all middlewares is that they implement the same interface as the object they're wrapping. This means a registry middleware must implement the `distribution.Namespace` interface, repository middleware must implement `distribution.Respository`, and storage middleware must implement `driver.StorageDriver`.
Currently only one middleware, cloudfront, a storage middleware, is included in the registry.