These days I have set up a #
git server for myself. I decided to keep it as simple as possible. Once a while I used #
gitea. I liked gitea.. well, I liked to use it - to be more precise. Basically I'm more a person who likes simple tools and gitea - of course - is not a simple piece of software.
It is a git repository management tool with a lot of features - like a wiki, an issue tracker, a kanban board, built-in ssh-server and things like that. Nice.. of course. Everything in one tool and due to the fact, that it is written in #
go all this in a single (statically linked) binary. My installation worked well for a while and I enjoyed to use it. Then a problem occured after installing updates and the server didn't start because the application crashed. For many reasons and circumstances I wasn't able to discovery the exact reason and one day I simply deleted the vhost and its data from the disk and dropped the database.
But I missed to have a git server and so I have set it up with pure git for now. To be able to access my stuff via web interface as well I just installed #
cgit. To be honest: I think cgit looks very old-fashioned and I didn't take a look at its produced html yet and also it is quite a simple tool and at least just a tool for browsing git repositories, but it has got some simple features that I really like in cgit... for example:
I browse the tree of a repository and select a specific file, then the file's content will show up. When I now click on the the "
log" tab then all commits show up that apply to that specific file. This is something that I really like. Ususally I do this on command line with
git log --follow <path/to/file> and I really like that I can do this in a web interface in such a simple way :-)
To have the ability to really manage repositories and permissions and stuff I want to extend the setup with #
gitolite. I used gitolite a while ago and really like it. For some reason it doesn't work as it used to. I can clone the gitolite-admin repo, change the config and push the changes to the server (push arrives as it should), but new repositories don't get set up at least - in other words: the process of script execution gets interrupted on the server. I have this problem on two different machines and I'm pretty sure the issue is related to the environment - some sort of special configuration or so. The steps I go to set it up are correct... I have a machine where I could make it work - at least it is not so hard to set it up.... yeah, but that's something I can try to debug slowly and when ready, then I can extend my setup quite easily.
For now I'm quite happy. With gitolite a few more things are be possible, that I like very much, but it's ok as it is now and when I have gitolite running again someday, i'll be happy :-)
Issue tracking is the next thing afterwards.
