Difference between revisions of "GitHostingSoftware"
m (Reverted edits by Wiki-Darkblue b (talk) to last revision by Strk) Tag: Rollback |
|||
(12 intermediate revisions by 3 users not shown) | |||
Line 6: | Line 6: | ||
=== '''GOGS''' === | === '''GOGS''' === | ||
+ | https://git.osgeo.org/gogs/ (main instance) | ||
+ | |||
* https://gogs.io/ | * https://gogs.io/ | ||
* http://jbrodriguez.io/gogs-an-alternative-to-gitlab/ | * http://jbrodriguez.io/gogs-an-alternative-to-gitlab/ | ||
− | * https://git.osgeo.org/ | + | * https://git.osgeo.org/gogs/org/sac/teams/gogs-service-writers |
* https://github.com/gogits/go-gogs-client | * https://github.com/gogits/go-gogs-client | ||
* https://discuss.gogs.io/t/how-to-manage-collaborators/87 | * https://discuss.gogs.io/t/how-to-manage-collaborators/87 | ||
+ | * https://notabug.org -- community hosted git repositories | ||
=== '''Github.com''' === | === '''Github.com''' === | ||
Line 21: | Line 24: | ||
=== '''GitLab''' === | === '''GitLab''' === | ||
+ | |||
+ | https://git.osgeo.org/gitlab/ (main instance) | ||
+ | |||
“You will be running Sidekiq, Unicorn, Nginx, Ruby (plus all its gems) | “You will be running Sidekiq, Unicorn, Nginx, Ruby (plus all its gems) | ||
and then Gitlab itself.” | and then Gitlab itself.” | ||
Line 81: | Line 87: | ||
''YA Feature Comparison Page'' | ''YA Feature Comparison Page'' | ||
* https://en.wikipedia.org/wiki/Comparison_of_source_code_hosting_facilities | * https://en.wikipedia.org/wiki/Comparison_of_source_code_hosting_facilities | ||
− | |||
== FOSS dot-org Git Implementations == | == FOSS dot-org Git Implementations == | ||
Line 136: | Line 141: | ||
Debian [https://anonscm.debian.org/cgit/pkg-grass '''pkg-grass'''] is maintained largely by <code>sebastic</code> Debian Developer (DD) | Debian [https://anonscm.debian.org/cgit/pkg-grass '''pkg-grass'''] is maintained largely by <code>sebastic</code> Debian Developer (DD) | ||
* https://qa.debian.org/developer.php?login=sebastic%40debian.org | * https://qa.debian.org/developer.php?login=sebastic%40debian.org | ||
+ | |||
+ | pkg-grass git branch guidelines https://pkg-grass.alioth.debian.org/policy/repositories.html#git-branches | ||
=== Kernel dot org Git === | === Kernel dot org Git === |
Latest revision as of 01:32, 20 April 2021
Some info to help with comparing git hosting software packages. See GitInfrastructureComparison
Git Server Software
GOGS
https://git.osgeo.org/gogs/ (main instance)
- https://gogs.io/
- http://jbrodriguez.io/gogs-an-alternative-to-gitlab/
- https://git.osgeo.org/gogs/org/sac/teams/gogs-service-writers
- https://github.com/gogits/go-gogs-client
- https://discuss.gogs.io/t/how-to-manage-collaborators/87
- https://notabug.org -- community hosted git repositories
Github.com
Dev-Info: https://developer.github.com/v3/ https://developer.github.com/v3/#authentication https://developer.github.com/webhooks/
GitLab
https://git.osgeo.org/gitlab/ (main instance)
“You will be running Sidekiq, Unicorn, Nginx, Ruby (plus all its gems) and then Gitlab itself.”
- https://about.gitlab.com/better-than-github/
- https://github.com/WebEntity/Installation-guide-for-GitLab-on-OS-X
- https://github.com/gitlabhq/gitlabhq/blob/8-0-stable/doc/instal/installation.md#advanced-setup-tips
- https://about.gitlab.com/downloads/
Kallithea
Q. can Kallithea add "static web pages" .. (perhaps with the "Apache sub-directory" setup?)
andrewsh on #kallithea:
technically, there's kallithea/public
directory, which you can put stuff into; it's just a directory where static files go if you use static_files = true
, it's around line 59 in kallithea/config/envirorment.py
, otherwise it's in your webserver's configuration. You can link that to the web interface using "Analytics" setting, there you can type there random HTML or JS stuff to modify the DOM whatever way you like.
cgit
- https://git.zx2c4.com/cgit/
- https://wiki.archlinux.org/index.php/Cgit#Configuration_of_Cgit
- http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git
- https://git.gnome.org/browse/
- https://anonscm.debian.org/git/
- https://sources.debian.net/stats/
gitbucket - JVM
GitHub.com issues UI infringement warning
gitblit - JVM
Phabricator + Diffusion
- https://secure.phabricator.com/book/phabricator/article/installation_guide/
- https://secure.phabricator.com/book/phabricator/article/diffusion/
- https://phabricator.wikimedia.org/T117071#2200208
gitolite
Apache Allura
- https://forge-allura.apache.org/docs/getting_started/installation.html#step-by-step-installation
- https://forge-allura.apache.org/p/allura/wiki/Feature%20Comparison/
Misc
Other Links
- https://git.wiki.kernel.org/index.php/InterfacesFrontendsAndTools
- http://gitolite.com/index2.html
- https://wiki.osgeo.org/wiki/SAC
- https://github.com/Soullivaneuh/trac2gitlab
YA Feature Comparison Page
FOSS dot-org Git Implementations
Apache Foundation Git
Please contact the infrastructure-dev@apache.org mailing list if you have comments or suggestions regarding this service.
Apache Software Foundation (ASF) infrastructure has evolved over more than a decade, with several major internal revisions, leading to the current implementations. ASF infrastructure design has concepts of mirrors (sites) and committers (people) built-in throughout. The ability of an ASF project to semi-autonomously create its own repositories and web presence, which then benefits from shared authentication, backup and other infrastructure services, is fundamental. Core servers were BSD and Solaris as well as Linux; small tools are often bash, perl, xslt and others; substantial backend engines are often implemented in java.
The 2013 U.S. Form 990 lists gross income for the ASF as $1.1 million, with $489k spent on infrastructure maintenance and development.
Guidelines for New Project Steering Committee Members: http://www.apache.org/dev/pmc.html#newcommitter http://www.apache.org/dev/pmc.html#SVNaccess
This tool is part of the committers-to-permissions chain: https://svn.apache.org/repos/asf/infrastructure/site/trunk/people/keys-fetch.py https://svn.apache.org/repos/asf/infrastructure/site/trunk/people/keys-README https://people.apache.org/keys/committer/
An example of an early 2000's era, xml
process to auto-generate sites with permissions:
https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/HowItWorks
Misc ASF entrypoint: https://svn.apache.org/repos/infra/infrastructure/trunk/projects/whimsy/www/secretary/workbench/worklist.cgi
ref: https://mail-archives.apache.org/mod_mbox/
A 2009 Infastructure Incident Report: https://blogs.apache.org/infra/entry/apache_org_downtime_initial_report
Debian Project Git
The Debian Project hosts extensive, custom-built project and package infrastructure including a comprehensive git interface using cgit, replacing an earlier gitweb system (when?).
cgit Browser:
https://anonscm.debian.org/cgit/
30,000 entries among four hundred eighty catagories.
Various ways to address content via URL:
- Project pkg-grass
https://anonscm.debian.org/cgit/pkg-grass
- Project qa Package
https://anonscm.debian.org/cgit/qa/debsources.git/
- Package Group
https://anonscm.debian.org/cgit/pkg-gnupg
- Package
https://anonscm.debian.org/cgit/pkg-gnupg/gnupg2.git/
- Username
https://anonscm.debian.org/cgit/users/eric/gnupg2.git/
gitweb Repository Browser Example:
Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-gnutls/libgcrypt.git;a=shortlog;h=refs/heads/branch1.6
Alioth.debian.org is a Debian server running FusionForge WIKI Git endpoints are integrated under Alioth (how? - see debsources above)
Debian pkg-grass is maintained largely by sebastic
Debian Developer (DD)
pkg-grass git branch guidelines https://pkg-grass.alioth.debian.org/policy/repositories.html#git-branches
Kernel dot org Git
05Mar2015 -- Linux Foundation System Administrator Konstanin Ryabitsev mentions gitolite and cgit LINK
https://git.kernel.org/cgit/ https://git.wiki.kernel.org/index.php/Main_Page
Wikimedia Foundation Git
twentyafterfour on #wikimedia-labs: phabricator might still be a decent way of managing your repositories; our phabricator accepts LDAP logins plus OAuth. It's essentially the same thing as gitolite but with a lot more automation around account management, key management and hooks. Phabricator integrates all of that into one package (which can still be somewhat automated / integrated with other tools) Gitolite likely doesn't support LDAP; certainly a lot lighter weight than Phab stack, if you are comfortable with perl and don't mind doing a bit of integration work; you have to deal with account management yourself.
mutante on #wikimedia-devtools says: we currently use gerrit for code review gerrit.wikimedia.org and gitblit for git.wikimedia.org. Things are being migrated to phabricator.wikimedia.org though diffusion. You are in the right channel. You can git clone all of our server configs btw. it's a puppet repo and all public. you might also be interested in wikitech.wikimedia.org, our labs environment where you can get free virtual machines to test things
Openstreetmap Internal Git
https://git.openstreetmap.org/
Libre Office Git
https://gerrit.libreoffice.org
Developer Wiki page: https://wiki.documentfoundation.org/Development
General Attributes of Git Hosts
- Implementation Language
- License
- Machine Resource Usage
Common Features
- Dashboard & File Browser
- Issue Tracking, Milestones & Commit keywords
- Organizations support
- Wiki
- Code Review
- GIST
- Web Hooks
Feature Comparison
- login via LDAP
- private repositories
- external issue tracker
- internal issue tracker
- tool to migrate from trac
- external wiki
- internal wiki
- organization management
- comment issues via mail
- PostgreSQL backend
- Multilanguage
- Comments on diff lines
- Pull requests
- Webhooks
- CL
- tracking of forks