Live data from Hacker News

Self-Hosting Git

peppe.rs

1–10 of 71 posts

Re: Self-Hosting Git

#3

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

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

  gitolite
  gitea, gogs
  gitlab

Re: Self-Hosting Git

#4
What is meant by "big corporates turning open-source into a T-shirt farming service" ?

Is the main point being made that, corporations are using open source (ie github) as a platform to commercialize software?

Re: Self-Hosting Git

#5
post #3

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

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

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

[2]: https://forgefed.peers.community/

[3]: https://src.fedoraproject.org/rpms/pagure

[4]: https://build.opensuse.org/package/show/openSUSE:Factory/pag...

[5]: https://packages.debian.org/sid/pagure

[6]: https://packages.ubuntu.com/focal/pagure

Re: Self-Hosting Git

#6
post #3

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

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

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.

Re: Self-Hosting Git

#7

What is meant by "big corporates turning open-source into a T-shirt farming service" ? Is the main point being made that, corporations are using open source (ie github) as a platform to commercialize software?

It probably refers to the controversy surrounding hacktoberfest: https://news.ycombinator.com/item?id=24643894

Re: Self-Hosting Git

#8
post #3

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

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

Plain ol' gitweb ain't bad either https://git-scm.com/book/en/v2/Git-on-the-Server-GitWeb

Re: Self-Hosting Git

#9
While i recently gave up self-hosting anything because i felt it was too time consuming, and instead i rely on public services like bitbucket for git hosting, i still have a Gitea instance running in docker on a host that is setup to mirror all my Bitbucket repositories.

While probably not really needed as Git repositories are self contained, i find it nice to have a "backup" on hand.

Re: Self-Hosting Git

#10

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

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.

Post reply on HN