summaryrefslogtreecommitdiffstats
path: root/gitolite (unfollow)
AgeCommit message (Collapse)AuthorFilesLines
2023-09-16gitolite: Prevent repo auto-creation on clone/fetchv0.2.0Malfurious1-1/+1
I'm considering this default behavior as a bug for normalmode. The creation of a repository via a read activity seems far too accidental for my taste. Repositories are created by pushing to them. This does mean that: git clone <new-url> ... git push is no longer a shorthand for: git init git remote add origin <new-url> ... git push I'm ok with that. Signed-off-by: Malfurious <m@lfurio.us>
2023-09-16gitolite: Fix bug in default branch push triggerMalfurious1-2/+1
Since it is now allowed to remove the remote default branch, this script needs to handle cases where there are no branches following a push. In this case, the `git symbolic-ref` command will fail, and we return our standard warning for when HEAD is dangling. Signed-off-by: Malfurious <m@lfurio.us>
2023-09-16Add host script for initial configuration flowMalfurious1-1/+5
The new installation procedure is to start with ./configure to set your pubkey up for admin access. The initialize script is updated to use an active prompt, since as-is, CTRL-C won't properly terminate the script to cancel. Signed-off-by: Malfurious <m@lfurio.us>
2023-09-15gitolite: Add admin initialization scriptMalfurious2-1/+17
Per docker image changes, this serves as an alternative entrypoint for performing initial pubkey configuration. Signed-off-by: Malfurious <m@lfurio.us>
2023-09-15gitolite: Allow users to delete remote HEAD branchesMalfurious1-0/+2
This allows the branch considered the repo default to be deleted via push. I'm not totally opposed to allowing this, even though it's not entirely necessary. However, the ability to do this is now required by the docker image entrypoint script. Signed-off-by: Malfurious <m@lfurio.us>
2023-09-15gitolite: Remove hard-coded admin usernameMalfurious1-1/+1
The default gitolite.conf file is now patched in to the gitolite installation in the docker image. This is so that the intended version of the file is used in the gitolite-admin repo from the very beginning. This is made necessary by the decoupling of repo purposes. Instead of using (literal) 'admin', '%ADMIN' will be substituted with the actual admin username during `gitolite setup`. Signed-off-by: Malfurious <m@lfurio.us>
2023-09-15gitolite: Correct site-local code locationMalfurious1-2/+2
Per the previous commit, site-local code is now to be located directly in the git user's home directory, as static content in the docker image. Correct this setting in the RC file. Signed-off-by: Malfurious <m@lfurio.us>
2023-09-15gitolite: Refactor Dockerfile for debian baseMalfurious2-0/+66
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-09-15gitolite: Consolidate config files into a single directoryMalfurious5-0/+264
The repository is being reworked to decouple its roles as normalmode source and gitolite-admin config. The gitolite-admin repository will be entirely separate. So there is no need to keep the conf or local directories around where they are at. Signed-off-by: Malfurious <m@lfurio.us>