Hi, On 7/13/05, Alvaro Lopez Ortega <[EMAIL PROTECTED]> wrote: > > (A CGI wrapper for SCRIPT_FILENAME env. variable? If so, any > > examples?) Also, is it possible to cope with this error by > > intervening cherokee internals? (Like adjusting it automatically > > from cherokee side.) Because, it's going to be very ugly to set > > SCRIPT_FILENAME in every PHP file you have. > > If the PHP engine were fully integrated with the rest of the server > you wouldn't need any of that, am I wrong?
IMHO, I hope so. As far as I can see from this position, intergrating PHP engine with the rest of the server will be the best solution. Otherwise, we'll need to code tons of messy stuff to make PHP scripts working well under current CGI interface. > I'm going to try to sort this issue out for the 0.4.25 release. Cool. Please don't get me wrong but, I'd be so appreciated to hear this features be completed ASAP. I liked Cherokee so much and want to use it in lots of projects in here. But we require some really critic features. (For example, a fully integrated PHP support is one of them.) > > 2. What should I do to make PHP work in a chroot'ed env.? > > [Hard]Linking PHP binaries inside DocumentRoot? > > The chroot and the document root don't have to be the same if you > don't want to, so you can do something like this: > > /var/www - Chroot > /var/www/bin > /var/www/lib > /var/www/htdocs - DocumentRoot > > Remember that the paths in the configuration must be relative to the > chroot one. I'm not so experienced in chroot'ing. Just wanted to learn if is there any possiblity to place PHP binary outside of chroot'ed directory. Now, you can say me that it's theoratically unfeasible. But when I look at the configuration file, I saw that we can configure log files in the outside of the chrooted directory. Is it possible to achieve sth. like this for PHP binaries too? Regards. _______________________________________________ Cherokee mailing list [email protected] http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee
