3 ms·

A worthy self-hostable Git Server too if you'd like to give it a try: https://www.scm-manager.org/

Legogris 6y ago
Others with some added functionality like web UI, in increasing line of complexity and features: gitolite gitea, gogs gitlab
- Conan_Kudo 6y ago
  There's also Pagure[1], which is in-between Gitea/Gogs and GitLab. Unlike most Git forges, Pagure has features that support decentralized development. For example, Pagure supports submitting pull requests with Git repos on any server (regardless of whether it's running Pagure or not) with its remote pull requests feature. Issues and pull request metadata are all stored as git repos using JSON files as data, making it easy and portable to other Pagure instances and easy to convert for any other system. There's development ongoing by one of the other contributors to build an extension for Pagure to support Forgefed[2], a protocol to federate and decentralize code project management. And unlike most Git forges, Pagure is really easy to deploy, update, and modify. Naturally, this means Pagure is packaged in virtually all major distributions[3][4][5][6], too. :) [1]: https://pagure.io/pagure https://pagure.io/pagure [2]: https://forgefed.peers.community/ https://forgefed.peers.community/ [3]: https://src.fedoraproject.org/rpms/pagure https://src.fedoraproject.org/rpms/pagure [4]: https://build.opensuse.org/package/show/openSUSE:Factory/pagure https://build.opensuse.org/package/show/openSUSE:Factory/pag... [5]: https://packages.debian.org/sid/pagure https://packages.debian.org/sid/pagure [6]: https://packages.ubuntu.com/focal/pagure https://packages.ubuntu.com/focal/pagure
  - Legogris 6y ago
    That looks really compelling, especially the decentralized collaboration functionality you mentioned. Haven't seen before, will check it out :)
- iKevinShah 6y ago
  I was using self hosted gitlab (plus runner) . It did the job perfectly well but was too resource heavy. Moved to Gitea and haven't looked back. Although extensibility / plugins are not there yet, but still for "git" it works wonders.
- nattaylor 6y ago
  Plain ol' gitweb ain't bad either https://git-scm.com/book/en/v2/Git-on-the-Server-GitWeb https://git-scm.com/book/en/v2/Git-on-the-Server-GitWeb
- stevekemp 6y ago
  Add gitbucket to your list too, it's a single .war file which makes deployment trivial, and it has a simple CI-system built in.
arichard123 6y ago
And if you need less than that you can do a lot just with SSH and file system permissions for read only deploy keys. I wrote a script that uses a directory structure with sym-linked ssh keys as a config for a to add/edit/remove ssh access. It appeals to me because I had gitlab for our 2 person team and it was just wrong sized for us. So many features went unused. Frequent upgrades meant an increasingly powerful server was required for doing basically nothing most of the time. CI/CD is not something we need.
- andrewzah 6y ago
  I find that gitlab is generally overkill. Gitea [0] is quite simple to deploy and uses much less resources. If you do want CI/CD later, you can integrate a self-hosted Drone [1] instance. [0]: https://github.com/go-gitea/gitea https://github.com/go-gitea/gitea [1]: https://github.com/drone/drone https://github.com/drone/drone
- OldHand2018 6y ago
  If you've got a small team such that managing SSH keys is reasonable, you can just keep using git over SSH and add CI/CD via githooks. It's honestly very, very easy - put an appropriately-named shell script in the directory and git automatically executes it. Just make a script called post-receive that kicks off your process when a push has been made. The script will receive all the information it needs to know what branch/ref changed. https://git-scm.com/docs/githooks https://git-scm.com/docs/githooks

Others with some added functionality like web UI, in increasing line of complexity and features: gitolite gitea, gogs gitlab

Conan_Kudo 6y ago
There's also Pagure[1], which is in-between Gitea/Gogs and GitLab. Unlike most Git forges, Pagure has features that support decentralized development. For example, Pagure supports submitting pull requests with Git repos on any server (regardless of whether it's running Pagure or not) with its remote pull requests feature. Issues and pull request metadata are all stored as git repos using JSON files as data, making it easy and portable to other Pagure instances and easy to convert for any other system. There's development ongoing by one of the other contributors to build an extension for Pagure to support Forgefed[2], a protocol to federate and decentralize code project management. And unlike most Git forges, Pagure is really easy to deploy, update, and modify. Naturally, this means Pagure is packaged in virtually all major distributions[3][4][5][6], too. :) [1]: https://pagure.io/pagure https://pagure.io/pagure [2]: https://forgefed.peers.community/ https://forgefed.peers.community/ [3]: https://src.fedoraproject.org/rpms/pagure https://src.fedoraproject.org/rpms/pagure [4]: https://build.opensuse.org/package/show/openSUSE:Factory/pagure https://build.opensuse.org/package/show/openSUSE:Factory/pag... [5]: https://packages.debian.org/sid/pagure https://packages.debian.org/sid/pagure [6]: https://packages.ubuntu.com/focal/pagure https://packages.ubuntu.com/focal/pagure
- Legogris 6y ago
  That looks really compelling, especially the decentralized collaboration functionality you mentioned. Haven't seen before, will check it out :)
iKevinShah 6y ago
I was using self hosted gitlab (plus runner) . It did the job perfectly well but was too resource heavy. Moved to Gitea and haven't looked back. Although extensibility / plugins are not there yet, but still for "git" it works wonders.
nattaylor 6y ago
Plain ol' gitweb ain't bad either https://git-scm.com/book/en/v2/Git-on-the-Server-GitWeb https://git-scm.com/book/en/v2/Git-on-the-Server-GitWeb
stevekemp 6y ago
Add gitbucket to your list too, it's a single .war file which makes deployment trivial, and it has a simple CI-system built in.

arichard123 6y ago

And if you need less than that you can do a lot just with SSH and file system permissions for read only deploy keys. I wrote a script that uses a directory structure with sym-linked ssh keys as a config for a to add/edit/remove ssh access. It appeals to me because I had gitlab for our 2 person team and it was just wrong sized for us. So many features went unused. Frequent upgrades meant an increasingly powerful server was required for doing basically nothing most of the time. CI/CD is not something we need.

andrewzah 6y ago
I find that gitlab is generally overkill. Gitea [0] is quite simple to deploy and uses much less resources. If you do want CI/CD later, you can integrate a self-hosted Drone [1] instance. [0]: https://github.com/go-gitea/gitea https://github.com/go-gitea/gitea [1]: https://github.com/drone/drone https://github.com/drone/drone
OldHand2018 6y ago
If you've got a small team such that managing SSH keys is reasonable, you can just keep using git over SSH and add CI/CD via githooks. It's honestly very, very easy - put an appropriately-named shell script in the directory and git automatically executes it. Just make a script called post-receive that kicks off your process when a push has been made. The script will receive all the information it needs to know what branch/ref changed. https://git-scm.com/docs/githooks https://git-scm.com/docs/githooks