use https as URL for repositories where available

Create issue
Issue #1576 closed
Frank Löffler created an issue

It would be nice to not have different access URLs for repositories depending on whether a user has write access or not. This too often leads to problems when checking something out as "read only" and trying to commit/push later.

I propose to have only one URL for repositories where this is possible. For most svn repositories this would mean not using plain http, and for git it would mean combining git@ and git:// into https:// (where possible, carpetcode-hosted repositories do not provide this right now).

Keyword:

Comments (4)

  1. Roland Haas
    • removed comment

    See #367 for related issues. For git we need to check that one can actually push into the alternative urls. If not the suggestion of supporting a pushurl (which git already supports) to be constructed from AUTH_URL would seem useful. This requires changes to GetComponents though.

  2. Frank Löffler reporter
    • removed comment

    For git the only URLs besides the self-hosted ones (Carpet, ect) work fine with https. Actually, this now seems to be the preferred method there (github).

  3. Frank Löffler reporter
    • changed status to resolved
    • removed comment

    Fixed now where possible. Repositories on carpetcode.org don't provide this. In order to use it there we either would need to provide https access, or move them to another hosting service.

  4. Log in to comment