Changes between Version 16 and Version 17 of GitolitePlan


Ignore:
Timestamp:
Aug 9, 2013 3:38:59 PM (2 years ago)
Author:
hvr
Comment:

update developer changes section

Legend:

Unmodified
Added
Removed
Modified
  • GitolitePlan

    v16 v17  
    4444=== Developer changes ===
    4545
     46Note: The `git.haskell.org` DNS CNAME alias for `ghc.haskell.org` has not been activated yet. If you want to try out the new smart-protocol `http://` urls, you can append "`88.198.224.241 git.haskell.org`" to your `/etc/hosts` file. For the non-`http://` protocols, you can just substitute `git.haskell.org` by `ghc.haskell.org` in the following instructions.
     47
     48==== Anonymous read access ====
     49
     50'''No immediate action needed'''
     51
     52The (old) `http://darcs.haskell.org/<repo-name>.git` Git URLs will continue to work (and still use [http://git-scm.com/book/en/Git-Internals-Transfer-Protocols#The-Dumb-Protocol The Dumb Protocol]) for some time.
     53
     54New `git clone` will use the new `http://git.haskell.org/<repo-name>.git` Git URLs and provide the much faster [http://git-scm.com/book/en/Git-Internals-Transfer-Protocols#The-Smart-Protocol "smart" Git/HTTP protocol]. Moreover, also access via `git://git.haskell.org/<repo-name>.git` is provided now.
     55
     56To rewrite a checked out to the new access URLs, you can use the `sync-all` script, e.g.:
     57
     58{{{
     59./sync-all -r git://ghc.haskell.org remote set-url origin
     60}}}
     61
     62==== Authenticated read/write access ====
     63
    4664For developers (with push permissions) who have already checked out repositories, the only change needed is to go over their repositories and update their git uris from
    4765
    48  `ssh://<user>@darcs.haskell.org/srv/darcs/<repo-name>`
     66 `ssh://<user>@darcs.haskell.org/srv/darcs/<repo-name>.git`
    4967
    5068to
    5169
    52  `ssh://[email protected]/<repo-name>`
     70 `ssh://[email protected]/<repo-name>.git`
    5371
    54 This can be accomplished either by editing their '.git/config' manually or using a Git command like `git remote set-url origin NEW-URL`.
     72This can be accomplished by invoking the `sync-all` script:
    5573
    56 The old Git `ssh://` URLs will continue to work, however, as the user won't have direct write permissions anymore at the filesystem level, they'll effectively become read-only URLs.
     74{{{
     75./sync-all -r ssh://[email protected] remote set-url origin
     76./sync-all -r ssh://[email protected] remote set-url --push origin
     77}}}
     78
     79~~The old Git `ssh://` URLs will continue to work, however, as the user won't have direct write permissions anymore at the filesystem level, they'll effectively become read-only URLs.~~
    5780
    5881Last but not least, the `sync-all` script needs to be adapted.