I'm looking for a self-hosted GitHub alternative that I can just plop into Portainer as a docker-compose and get working.
My main interest is in something that sort of works with GitHub - if there's a way I can pull repos from GitHub into this self-hosted git using a webUI and maybe even push my changes to repos on GitHub, that would be nice. I'm not hard-and-fast on this though as this is mostly an experiment right now and I don't know why I need this.
What are you folks using to host your super secret local code and why?
Obligatory check : are you sure you really need a forge? (that's the name we use to designate tools like Github/Gitlab/Gitea/etc). You can do a lot with git alone : you can host repositories on your server, clone them through ssh (or even http with git http-backend, although it requires a bit of setup), push, pull, create branches, create notes, etc. And the best of it : you can even have CI/CD scripts as post-receive hooks that will run your tests, deploy your app, or reject the changes if something is not right.
The only thing you have to do is to create the repos on your server with the --bare flag, as in git init --bare, this will create a repos that is basically only what you usually have in the .git directory, and will avoid having errors because you pushed to a branch that is not the currently one checked. It will also keep the repos clean, without artifacts (provided you run your build tasks elsewhere, obviously), so it will make all your sources really easy to backup.
And to discuss issues and changes, there is always email. :) There is also this, a code review tool that just pop up on HN.
And it works with Github! :) Just add a git remote to Github, and you can push to it or fetch from it. You can even setup hooks to sync with it. I publish my FOSS projects both on Github and Gitlab, and the only thing I do to propagate changes is to push to my local bare repos that I use for easy backups, they each have a post-update hook which propagates the change everywhere it needs to be (on Github, Gitlab, various machines in my local network, which then have their own post-update hooks to deploy the app/lib). The final touch to that : having this ~/git/ directory that contains all my bare repos (which are only a few hundred MB so fit perfectly in my backups) allowed me to create a git_grep_all script to do code search in all my repos at once (who needs elasticsearch anyway :D ) :
#!/usr/bin/env bash
# grep recursively bare repos
INITIAL_DIR=$(pwd)
for dir in $(find . -name HEAD -exec dirname '{}' \;); do
pushd $dir > /dev/null
git grep "$*" HEAD > /dev/null
if [[ "$?" = "0" ]]; then
pwd
git grep "$*" HEAD
echo
fi
popd > /dev/null
done
(note that it uses pushd and popd, which are bash builtins, other shells should use other ways to change directories)
The reason why you may still want a forge is if you have non tech people who should be able to work on issues/epics/documentation/etc.
And forgejo runner is basically github actions, I just started automating a lot of my personal projects.
(it's in alpha state, but my basic actions haven't had any problems)
I also recommend forgejo, I've been using it for a while for my personal projects and the ui is still beautiful while being a simple git server at the same time.
What? Gitea. Gitlab is a complete devops platform. Awesome, but complete overkill.
Why? Because I regularly commit code atrocities and have a hard enough time dealing with imposter syndrome, I don't need to add public shaming on top of it
(And just data sovereignty I guess)
Why instead of gitea though? I thought the “for profit” stuff was only to provide the original developers of gitea the ability to provide paid support to commercial clients.
And is hilariously overkill for what OP seems to want. It's a pretty large and heavy package that comes with a whole lot of (for OP unnecessary) features.
My experience was that they were definitely overkill until they weren't, and I was glad to be comfortable in the UI when I wanted to start playing with more advanced features. Something like the sameersbn/gitlab docker image can get you started and grow with you a ton.
What are you folks using to host your super secret local code and why?
This obviously doesn't help for the rest of your question, but for anything that I don't want to open source for whatever reason, I just make a bare repo and push it to a folder on my server that has all my bare repos. Literally just git server on my LAN. Nothing fancy. No UI or anything, but I don't use a UI for git anyway.
If you don't have a server at home, you could do the same thing but to a folder on your local machine. That obviously means you will have no backup. But you will still have version control in case you want to revert something you did or refer back to an old version.
I currently use GitLab, but if I were doing things from the start I'd go with Gitea or Forgejo since its lighter. Though I do quite like GitLab CI (which is why I didn't go with the other initially) but these days I hear Gitea has Actions support built in.
Gitlab also has issues, error tracking via sentry and much more. If you want only something nice to host your code go with Gitea, if you also want to manage your project or do auto releases, use gitlab.
I personally use gitea but there is also a community version of gitlab that has way more power than I need.
Gitea can import a repo from GitHub but I don't know whether it can also push updates out as one never tried to do that.
I picked gitea as I didn't need all of the extra power of gitlab and they were the first two options I found. I don't deploy it using portainer but all of my stacks are set up as git repos in portainer and using the webhook feature it'll auto pull and redeploy whenever I push to it
Without knowing why you need a local GitHub like tool is almost impossible to suggest, but I know Gogo's can keep a remote in sync if you need. Also there is a python tool to backup your GitHub account and or organisation