Feature #491

Provide https access to git repository

Added by herck over 6 years ago. Updated about 6 years ago.

Status:RejectedStart date:11 Nov 2013
Priority:NormalDue date:
Assignee:herck% Done:

0%

Category:-
Target version:Sprint 19

Description

People sitting behind strict firewalls (e.g. A. Glavic) might not have access to the usual git:// repo

History

#1 Updated by wuttke over 6 years ago

  • Status changed from Backlog to Sprint
  • Assignee set to wuttke

#2 Updated by wuttke over 6 years ago

  • Assignee deleted (wuttke)

potentially dangerous; needs support by Christian

#3 Updated by wuttke over 6 years ago

I think gitweb does not help here (rather duplicates functionality we have in redmine repository view).
I rather think, we need something like git-http-backend.

#4 Updated by herck over 6 years ago

  • Target version set to Sprint 18

#5 Updated by herck over 6 years ago

  • Assignee set to herck

#6 Updated by herck over 6 years ago

  • Target version changed from Sprint 18 to Sprint 19

#7 Updated by herck about 6 years ago

  • Status changed from Sprint to Rejected

For access to a read-only git:// repository, the user needs to have port 9418 open, which is commonly blocked by corporate firewalls. The user thus needs to ask to open this port for her. No problems exist with the ssh protocol (which is used when cloning from git@apps...). The benefit of providing https access is not worth the effort for the time being.

Also available in: Atom PDF