On Thu, Dec 4, 2008 at 10:59 AM, Thomas Johnson <[EMAIL PROTECTED]> wrote:
> I am working on implementing a mercurial controller in my application.
> So far I am able to clone and pull from it without any troubles. I
> only push via ssh so I am not sure if it is supported. Here is a
> simplified version of what I am using -
> http://pylonshq.com/pasties/1022. Anyways, I would now like to
> implement authentication for clones/pulls and was wondering if you
> guys have any suggestions as to a good method e.g. basic auth, digest,
> etc.

hello, auth for mercurial is done independently of the system so the
answer is that your auth works for everything else.

I have been playing around with the code from twsite (tosca widgets
site) and had a bug with paste.auth (which it uses) + mod_wsgi you can
google for those mails at the mod_wsgi list, but it works really well
for mod_proxy + paster setup

I currently have plans to migrate it's auth to repoze.who/what but
that's after I'm done with some intensive work i'm stuck into now.

here is the clone for the site, it's a pylons app so all you have to
do is understand it's controller. it even has methods for creating
repo's over the web, very handy :) I got some non-public changes on my
local mercurial repo which upgrade it in small ways, nothing fancy yet
but if you are interested I could push it somewhere. Alberto already
said I should do it at the tw site but I haven't yet.

anyway here is the link
http://toscawidgets.org/hg/twWebSite/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to