[SciPy-dev] The future of SciPy and its development infrastructure
Mon Feb 23 20:48:43 CST 2009
On Mon, Feb 23, 2009 at 20:42, Pauli Virtanen <email@example.com> wrote:
> Mon, 23 Feb 2009 19:40:27 -0600, Robert Kern wrote:
>> Pauli, you seem familiar with setting up a git-to-svn bridge. Can you do
> Sure. I'll need a box on which to deploy the update script, though.
> Would one (which?) of the virtual hosts of conference.scipy.org do?
Probably. That machine is where all of the services will be moving to.
Peter might be able to say which one.
> I'd guess what's needed of the web server would be only to enable CGI for
> a single script. When poked, it would then fetch new stuff from SVN and
> - Push to github or some such service
> - Push to a HTTP location on the machine, served statically
> - Push to a HTTP location on the machine, served by gitweb (cgi)
> The first option is probably the easiest, if account/password issues can
> be sorted out. The second option is probably enough for practical
1) probably has the advantage of having smaller overhead for people
publishing their own branches on github.
>> What do you need done one the actual SVN server to support this?
> A post-commit hook poking a CGI script somewhere should be enough:
> /usr/bin/curl -d "revision=$REV&repository=$REPOS" \
> http://host/path/to/script.cgi &
> If all this runs on the same machine as the SVN server, going over the
> network can be skipped, too.
> Anyway, I'll think about the details tomorrow.
Great. Thank you!
"I have come to believe that the whole world is an enigma, a harmless
enigma that is made terrible by our own mad attempt to interpret it as
though it had an underlying truth."
-- Umberto Eco
More information about the Scipy-dev