Automating the build of this image will be awkward if we need a
user-supplied input file each time.  At best, it will probably lead to
building out of per-instance configuration branches that store the
file...

The initial administrator pubkey is only really needed to include in the
first image that is run at any given site, since a new install doesn't
have a config/repository datastore yet.  Once that is the case, the
procedure in the Dockerfile to init the /var/lib/gitolite directory (now
refactored to a shell script file) can be skipped, since that directory
will be replaced by the previous container's volume.

This is probably not the final form of this kind of build design change,
but will work for now to get up and running easily with cychedelic.

Signed-off-by: Malfurious <m@lfurio.us>

Provide a config file for the back-end SSH daemon.  Primarily, this
explicitly disables root login, password auth, and additional
unnecessary frills.  Additionally, the sftp subsystem is omitted.

Now that this file is added, hostkey files (and the external volume
containing them) are moved to a new dedicated location (/hostkeys/...).
This allows us to bake sshd_config into the built gitolite image,
instead of it also living in the external volume.  This makes it easier
for future changes to be incorporated by simply updating the image.

Signed-off-by: Malfurious <m@lfurio.us>

This is useful as documentation to the user, but can be necessary to
work with some docker-compose setups.

Signed-off-by: Malfurious <m@lfurio.us>

For compatibility with the front-end docker image, ensure git
repositories (and their parent directories) have mode 0755, aka: go+rx.

Signed-off-by: Malfurious <m@lfurio.us>

Signed-off-by: Malfurious <m@lfurio.us>

Signed-off-by: Malfurious <m@lfurio.us>

Signed-off-by: Malfurious <m@lfurio.us>