Trying to clone the git repository has the same options on the Project > Code page.
"Hello World Project Example"
RW: git clone http://alfmatos@opensourceprojects.eu/git/p/helloworld/code-0 helloworld-code-0
RO: git clone http://alfmatos@opensourceprojects.eu/git/p/helloworld/code-0 helloworld-code-0
HTTP: git clone https://alfmatos@opensourceprojects.eu/git/p/helloworld/code-0 helloworld-code-0
Only difference is http, which is in fact HTTPS.
The clone urls should be different, correct?
Discussion
-
Rui Ferreira
2013-04-18No they should be the same
The username is only needed for Write operations (of if the repo is private)
It should be HTTPS but HTTP is (still) enabledBottom line is, RO/RW/HTTP could be replaced with a single entry (or two to make the read only case clearer).
-
Alfredo Matos
2013-04-18I assumed that:
RO should be public git glone
RW should be git clone through ssh (auth with keys)
HTTP should be HTTP clone (RO)No? We can turn a few things off while not ready (e.g. RO/RW , which are meant to be done over ssh, right?)
-
Rui Ferreira
2013-04-18That is the regular meaning of those three yes? RW is also HTTPS+password.
We currently do not support SSH access to the repos. Is this criticall if we can provide Authenticated access over HTTPS?
-
Alfredo Matos
2013-04-18Not at the moment, provided that RW and RO works over HTTP. But there must be some indication on how to actually get it to work :).
-
Rui Ferreira
2013-04-18Ok, I've changed the template to have a single URL. Still need to:
apply some style to it
point to some help/common issues
-
Carla Leite
2013-04-24- labels: code, git --> code, git, style
-
Rui Ferreira
2013-04-29- labels: code, git, style --> code, git, style, ui
- assigned_to: Carla Leite
-
João Paulo Barraca
2013-05-08We should present an URI using HTTPS when the access is authenticated.
This would avoid users sending their passwords in clear.
-
João Paulo Barraca
2013-05-08- assigned_to: Carla Leite --> nobody
-
Rui Ferreira
2013-05-09Clone URLs are now HTTPS.