summaryrefslogtreecommitdiffstats
path: root/docker/gitolite_init.sh (unfollow)
AgeCommit message (Collapse)AuthorFilesLines
2023-09-15gitolite: Refactor Dockerfile for debian baseMalfurious1-6/+0
Building from debian:latest will make for a smaller image, a faster build, and will make the image more accessible to a wider variety of platforms. The effort started by 19e7dc8932c is expanded upon such that the image cleanly bakes in all static config files into the image - ie. the entire hosting user's home directory, except for the repositories directory. This removal of config management from the gitolite-admin repo is part of the reason why it is being decoupled from this repo. The gitolite image will now never utilize a user pubkey during build. Instead, it can be invoked with an alternative entrypoint to interactively configure a new install. Signed-off-by: Malfurious <m@lfurio.us>
2023-08-12gitolite: Make admin pubkey an optional input to Docker imageMalfurious1-0/+6
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>