Hi Galen!

On Thu, Jun 4, 2009 at 13:33, Galen Charlton <galen.charl...@liblime.com> wrote:

> Cloning and fetching over HTTP now works:
>
> git clone http://git.koha.org/pub/scm/koha.git kohaclone
>
> Note that because this requires a cronjob (git-update-server-info)
> that I have set running every 10 minutes, cloning or fetching over
> HTTP can result in a repo that's slightly out of date with respect to
> the public repo.  As a general note, unless you absolutely have to use
> HTTP because of restrictive firewall rules, using the Git protocol is
> more efficient.

That's great! Thank you very much for the lightning quick setup! I
tested it now and it's working. :)

I see that you have also already updated the wiki page accordingly:

Version Control for Koha using Git    [Koha Developer Wiki]
http://wiki.koha.org/doku.php?id=en:development:git_usage

------------------------------
Cloning over HTTP

To clone the repo using the Git protocol (git:), you need to be able
to connect to port 9418 on git.koha.org. If for some reason you have a
restrictive firewall that cannot be changed, and using SSH port
forwarding is not an option, it is possible to clone the repo using
HTTP:

  git clone http://git.koha.org/pub/scm/koha.git kohaclone

Other git operations such as git fetch and git rebase will work
normally over you clone using HTTP.

Note that because this requires a cronjob (git-update-server-info)
that is set to run every 10 minutes, cloning or fetching over HTTP can
result in a repo that's slightly out of date with respect to the
public repo. As a general note, unless you absolutely have to use HTTP
because of restrictive firewall rules, using the Git protocol is more
efficient, both for you and the server that hosts the repository.
-----------------------------


Thank you also for updating the documentation about git in the Koha
Developer wiki!  :)

Cheers,
Ricardo
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel

Reply via email to