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

Make the index.html files the visible overview menu entry

Browse source 
And move menu entry definition into a page that the user has no reason to navigate to

Signed-off-by: Sven Dowideit <SvenDowideit@home.org.au>
This commit is contained in:
Sven Dowideit 2016-05-19 12:52:58 +00:00
parent a5f72a6032
commit 3069a04b8c
34 changed files with 180 additions and 122 deletions
Download patch file Download diff file Expand all files Collapse all files

12
docs/deploying.md
View file

@ -11,7 +11,7 @@ weight=3
# Deploying a registry server
You need to [install Docker version 1.6.0 or newer](https://docs.docker.com/installation/).
You need to [install Docker version 1.6.0 or newer](/engine/installation/index.md).
## Running on localhost
@ -39,7 +39,7 @@ To stop your registry, you would:
## Storage
By default, your registry data is persisted as a [docker volume](https://docs.docker.com/userguide/dockervolumes/) on the host filesystem. Properly understanding volumes is essential if you want to stick with a local filesystem storage.
By default, your registry data is persisted as a [docker volume](/engine/userguide/containers/dockervolumes.md) on the host filesystem. Properly understanding volumes is essential if you want to stick with a local filesystem storage.
Specifically, you might want to point your volume location to a specific place in order to more easily access your registry data. To do so you can:
@ -180,7 +180,7 @@ Seeing X509 errors is usually a sign you are trying to use self-signed certifica
### Alternatives
1. You may want to leverage more advanced basic auth implementations through a proxy design, in front of the registry. You will find examples of such patterns in the [recipes list](recipes.md).
1. You may want to leverage more advanced basic auth implementations through a proxy design, in front of the registry. You will find examples of such patterns in the [recipes list](recipes/index.md).
2. Alternatively, the Registry also supports delegated authentication, redirecting users to a specific, trusted token server. That approach requires significantly more investment, and only makes sense if you want to fully configure ACLs and more control over the Registry integration into your global authorization and authentication systems.
@ -192,7 +192,7 @@ Beware that you will have to implement your own authentication service for this
As your registry configuration grows more complex, dealing with it can quickly become tedious.
It's highly recommended to use [Docker Compose](https://docs.docker.com/compose/) to facilitate operating your registry.
It's highly recommended to use [Docker Compose](/compose/index.md) to facilitate operating your registry.
Here is a simple `docker-compose.yml` example that condenses everything explained so far:
@ -226,7 +226,7 @@ You will find more specific and advanced informations in the following sections:
- [Configuration reference](configuration.md)
- [Working with notifications](notifications.md)
- [Advanced "recipes"](recipes.md)
- [Advanced "recipes"](recipes/index.md)
- [Registry API](spec/api.md)
- [Storage driver model](storagedrivers.md)
- [Storage driver model](storage-drivers/index.md)
- [Token authentication](spec/auth/token.md)