If you want even more minimal, Gerrit is structured as a Java app with no external dependencies like databases, and stores all it's configuration and runtime information on the filesystem, mostly as data structures in the git repos.

Shared filesystems is all you need to scale/replicate it, and it also makes the backup process quite simple.

▲

hk1337 5 hours ago | parent | next [-]

I might be one of the few that is intrigued by this being that it’s Java but this looks really neat. Does it do git repositories like gitea, GitHub, etc, or is it more of a project management site for the repositories? They describe it as “code review”, so I wasn’t sure.

I’m a little put off on the google connection but it seems like it could run rather independently.

	▲	zdw 9 minutes ago \| parent \| next [-]
		It's hyper-focused on code review and CI integration, which it does really well. It's not focused on all the other stuff that people think of in code forges (hosting the README in a pretty way, arbitrary page hosting, wiki, bug tracking, etc.) but can be integrated with 3rd party implementations of those fairly trivially.
	▲	arccy 2 hours ago \| parent \| prev [-]
		It necessarily hosts a git server (using jgit), but the primary interface is as a code review tool. even browsing the git repos it hosts uses an embedded version of another tool (gitiles). https://gerrithub.io/ is a public instance

▲

Kwpolska 4 hours ago | parent | prev [-]

The deployment may be simple, but at the same time, the Gerrit code review workflow is terrible.

	▲	zdw 32 minutes ago \| parent [-]
		I personally find the rebase and stacking commit focused method of integration that Gerrit uses to be easier and cleaner than PR's in GitHub. Having done CI integrations with both, Gerrit's APIs send pre- and post-merge events through the same channel, instead of needing multiple separate listeners like GitHub.