Sebastiaan van Stijn 129c9a22f7 Fix headers in documentation

These headers were rendered as body text
because there was no space, but a "tab" after
the `#`.

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

2015-12-12 01:39:51 +01:00

Recipes

You will find here a list of "recipes", end-to-end scenarios for exotic or otherwise advanced use-cases.

Most users are not expected to have a use for these.

Requirements

You should have followed entirely the basic deployment guide.

If you have not, please take the time to do so.

At this point, it's assumed that:

you understand Docker security requirements, and how to configure your docker engines properly
you have installed Docker Compose
it's HIGHLY recommended that you get a certificate from a known CA instead of self-signed certificates
inside the current directory, you have a X509 domain.crt and domain.key, for the CN myregistrydomain.com
be sure you have stopped and removed any previously running registry (typically docker stop registry && docker rm -v registry)