Hi, You can find a tutorial like that here: http://www.howtoforge.com/how-to-install-and-configure-cherokee-web-server-with-php5-and-mysql5-on-ubuntu-8.10
----- Wiadomość oryginalna ----- Od:: [email protected] Data:: Czwartek, 29 Styczeń 2009 12:00 Temat: Cherokee Digest, Vol 7, Issue 35 > Send Cherokee mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.octality.com/listinfo/cherokee > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Cherokee digest..." > > > Today's Topics: > > 1. Installation for Newbies (Robert Rademacher) > > > ------------------------------------------------------------------- > --- > > Message: 1 > Date: Wed, 28 Jan 2009 17:48:06 -0800 (PST) > From: Robert Rademacher <[email protected]> > Subject: [Cherokee] Installation for Newbies > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset="us-ascii" > > Hi all, > > Someone may want to document the installation procedure for pre- > requisition prior to installing cherokee web server in > www.cherokee-project.com web site. > > Here's the good tip (nginx) from that web site to be used for > writing the pre-requisition (such as installing mysql, libraries, > php modules, etc.): > > http://howtoforge.org/installing-nginx-with-php5-and-mysql-support- > on-fedora-10-p2 > > I know Cherokee is bit different from nginx. The main thing that > sets Cherokee apart from nginux is the excellent support for cgi- > bin (I write my own C executable scripts), as well as better > documentation. Let's make Cherokee to be better than nginx. > > Thanks, > > Robert > > > > > ________________________________ > From: "[email protected]" <cherokee- > [email protected]>To: [email protected] > Sent: Wednesday, January 28, 2009 6:00:01 AM > Subject: Cherokee Digest, Vol 7, Issue 34 > > Send Cherokee mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.octality.com/listinfo/cherokee > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Cherokee digest..." > > > Today's Topics: > > 1. 'Dynamic' url based authentication (Jesse van den Kieboom) > 2. Re: 'Dynamic' url based authentication (Alvaro Lopez Ortega) > 3. Re: 'Dynamic' url based authentication (Jesse van den Kieboom) > > > ------------------------------------------------------------------- > --- > > Message: 1 > Date: Wed, 28 Jan 2009 08:57:21 +0100 > From: Jesse van den Kieboom <[email protected]> > Subject: [Cherokee] 'Dynamic' url based authentication > To: [email protected] > Message-ID: <1233129441.27250.3.ca...@wren> > Content-Type: text/plain > > Hi, > > I'm exploring the possibilities of a replacement for apache, and > cherokee seems a very attractive sollution. I have one need though > thatI could not directly find in the documention. Being able to > authenticateusers given the url they try to access, dynamically. > With this I mean > that for instance I'd like to match the first directory in a url and > match that to a user group in ldap, e.g. http://example.com/myproject/ > would be authenticated against ldap users in the group myproject. Is > this possible with cherokee? And if not, maybe there is another > way to > do this without configuring every single directory? > > > > -- > Jesse van den Kieboom > > Personal: http://www.icecrew.nl > Professional: http://www.novowork.com > > > > ------------------------------ > > Message: 2 > Date: Wed, 28 Jan 2009 09:37:24 +0100 > From: Alvaro Lopez Ortega <[email protected]> > Subject: Re: [Cherokee] 'Dynamic' url based authentication > To: Jesse van den Kieboom <[email protected]> > Cc: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes > > On 28-ene-09, at 08:57, Jesse van den Kieboom wrote: > > > I'm exploring the possibilities of a replacement for apache, and > > cherokee seems a very attractive sollution. I have one need > though > > that > > I could not directly find in the documention. Being able to > > authenticate > > users given the url they try to access, dynamically. With this I > mean> that for instance I'd like to match the first directory in a > url and > > match that to a user group in ldap, e.g. > http://example.com/myproject/> would be authenticated against ldap > users in the group myproject. Is > > this possible with cherokee? And if not, maybe there is another > way to > > do this without configuring every single directory? > > It isn't possible yet. Actually, a variable substitution mechanism > has > been a frequent request, so I think we will add it the upcoming > release (or the one after). > > Do you have a more detailed example about what you'd need it to do? > I'd like to be sure that the implementation fits the needs of the > people who has requested it. > > -- > Octality > http://www.octality.com/ > > > > ------------------------------ > > Message: 3 > Date: Wed, 28 Jan 2009 09:47:26 +0100 > From: Jesse van den Kieboom <[email protected]> > Subject: Re: [Cherokee] 'Dynamic' url based authentication > To: Alvaro Lopez Ortega <[email protected]> > Cc: [email protected] > Message-ID: <1233132446.27250.9.ca...@wren> > Content-Type: text/plain > > Op woensdag 28-01-2009 om 09:37 uur [tijdzone +0100], schreef Alvaro > Lopez Ortega: > > On 28-ene-09, at 08:57, Jesse van den Kieboom wrote: > > > > > I'm exploring the possibilities of a replacement for apache, and > > > cherokee seems a very attractive sollution. I have one need > though > > > that > > > I could not directly find in the documention. Being able to > > > authenticate > > > users given the url they try to access, dynamically. With this > I mean > > > that for instance I'd like to match the first directory in a > url and > > > match that to a user group in ldap, e.g. > http://example.com/myproject/> > would be authenticated against > ldap users in the group myproject. Is > > > this possible with cherokee? And if not, maybe there is > another way to > > > do this without configuring every single directory? > > > > It isn't possible yet. Actually, a variable substitution > mechanism has > > been a frequent request, so I think we will add it the upcoming > > release (or the one after). > > Cool! > > > Do you have a more detailed example about what you'd need it to do? > > I'd like to be sure that the implementation fits the needs of > the > > people who has requested it. > > What I would like to use it for is managing remote git repositories > including authentication in an easy way, using ldap to authenticate > users. > > So, my layout could be: > > http://example.com/git -> /var/www/git > > with /var/www/git including any number of repos.git directories. I'd > like to map something like http://example.com/git/([^/]+).git to > authentication based on users in the group $1. Being able to > substituteregular expression groups from a Regular Expression rule > in certain > fields would do the trick I think (although I'm not sure the ldap > authentication module is flexible enough to allow this, e.g. is the > Users field mandatory, because I'd like to match users based on a > customfilter with the regex group substituted). > > > -- > > Octality > > http://www.octality.com/ > > > -- > Jesse van den Kieboom > > Personal: http://www.icecrew.nl > Professional: http://www.novowork.com > > > > ------------------------------ > > _______________________________________________ > Cherokee mailing list > [email protected] > http://lists.octality.com/listinfo/cherokee > > > End of Cherokee Digest, Vol 7, Issue 34 > *************************************** > > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: http://lists.octality.com/pipermail/cheroke > > ------------------------------ > > _______________________________________________ > Cherokee mailing list > [email protected] > http://lists.octality.com/listinfo/cherokee > > > End of Cherokee Digest, Vol 7, Issue 35 > *************************************** > _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
