Em 27-06-2011 05:30, Marius Mårnes Mathiesen escreveu:
On Sun, Jun 26, 2011 at 7:42 PM, <jarrod.rober...@gmail.com <mailto:jarrod.rober...@gmail.com>> wrote:

    Yes, lots of people disable the HTTP support completely and only
    use SSH for writes and Git of read only access. This is what we do
    for our installation.
    This is very important for work flows where people should be able
    to check out read only copies but not be able to write.


I'd argue that requiring different URLs for reading and writing is more cumbersome than using the same one and then using authentication/authorization to handle requests to write to the repository.

    There is already what looks like a nice Chef recipe for Ubuntu, we
    don't do Ubuntu because we have standardized on RHEL5/CentOS5
    because that is what all our clients use, an RPM package and a
    custom YUM repository for RHEL5/CentOS5.x that at least
    consolidated all the very specific Ruby/Rails/Passenger details
    into a single RPM and have dependencies on all the other stuff
    like Apache, MySQL, etc. would go a long way to a more painless
    adoption.


It would be wonderful if someone would step up and take responsibility for .rpm/.deb packages of Gitorious, nothing would be better. Last time I checked there weren't packages for some of the dependencies (activemq, sphinx), they'd need to be maintained as well. As for Passenger, it seems Fedora/RedHat won't include that for some time: https://bugzilla.redhat.com/show_bug.cgi?id=470696

Hi Marius, although there is no ActiveMQ package for Debian, there is the stompserver package that could be used instead. Sphinx exists like sphinxsearch package in Debian (I believe in Ubuntu too). There is also 'libapache2-mod-passenger'.

Not that it would be simple to write such gitorious.deb package, but I don't think the main reasons are the lack of packages, in Debian at least... :)

--
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com

Reply via email to