Differences between revisions 2 and 4 (spanning 2 versions)
⇤ ← Revision 2 as of 2009-05-19 19:31:00 →
Size: 724
Editor: localhost
Comment: converted to 1.6 markup
← Revision 4 as of 2012-05-08 15:11:05 → ⇥
Size: 936
Editor: mpm
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
<<Include(A:style)>>
<<Include(A:stub)>>
Line 3: Line 6:
hgwebproxy was written by Jesper Noehr (jesper@noehr.org), with minor
modifications by Faheem Mitha (faheem@email.unc.edu). It uses code
from https://bitbucket.org/jespern/cx/. Hgwebproxy uses Django as a
proxy for hgweb. In other words, when the request is sent to hgweb,
Django gets it and relays it to hgweb, and then intercepts the
response from hgweb, and can do post-processing on it if
necessary. This has two advantages. One, hgweb can be put behind
Django auth. Secondly, this makes it possible to use Django templating
with hgweb.		 hgwebproxy was written by Jesper Noehr ( jesper@noehr.org ), with minor modifications by Faheem Mitha ( faheem@email.unc.edu ). It uses code from https://bitbucket.org/jespern/cx/. Hgwebproxy uses Django as a proxy for hgweb. In other words, when the request is sent to hgweb, Django gets it and relays it to hgweb, and then intercepts the response from hgweb, and can do post-processing on it if necessary. This has two advantages. One, hgweb can be put behind Django auth. Secondly, this makes it possible to use Django templating with hgweb.
Line 13: Line 8:
To try out this project, clone http://www.bitbucket.org/faheem/hg
and read README at top level.		 To try out this project, clone http://www.bitbucket.org/faheem/hg and read README at top level.

Is Available a new fork of faheem app, [[http://bitbucket.org/mariocesar/django-hgwebproxy/overview|Django Hgwebproxy]] fully integrated to the django admin interfaces.

{i} This page does not meet our wiki style guidelines. Please help improve this page by cleaning up its formatting.

{i} This page is an incomplete stub. Please help improve this page by expanding it, following our wiki style guidelines.

From the README at http://www.bitbucket.org/faheem/hg/src/tip/README.

hgwebproxy was written by Jesper Noehr ( jesper@noehr.org ), with minor modifications by Faheem Mitha ( faheem@email.unc.edu ). It uses code from https://bitbucket.org/jespern/cx/. Hgwebproxy uses Django as a proxy for hgweb. In other words, when the request is sent to hgweb, Django gets it and relays it to hgweb, and then intercepts the response from hgweb, and can do post-processing on it if necessary. This has two advantages. One, hgweb can be put behind Django auth. Secondly, this makes it possible to use Django templating with hgweb.

To try out this project, clone http://www.bitbucket.org/faheem/hg and read README at top level.

Is Available a new fork of faheem app, Django Hgwebproxy fully integrated to the django admin interfaces.

HgWebProxy (last edited 2012-05-08 15:11:28 by mpm)