Hello Pascal! On 29-oct-08, at 11:42, Pascal Varet wrote:
> Firstly, is there or will there be a way to activate keepalives per > virtual host, as opposed to the whole server? Keepalives speed up the > serving of static content but murder the performance of dynamic > applications, so under Lighttpd I have a virthost with keepalives for > static contents and a virthost without keepalive for Django proper. As > a rule of thumb, different server parameters for different virtual > hosts would be extremely useful for all sorts non-trivial setups, but > it's really the keepalives that will make or break the deal for me. That's a good point, actually. I have just logged it as a RFE: http://code.google.com/p/cherokee/issues/detail?id=181 Most probably it will be implemented in Cherokee 0.11. > Next, is there a way to make StaticGenerator > (http://superjared.com/projects/static-generator/) work? It requires > that the server be able to serve a static index.html file if it exists > at the requested path, and delegate the request to Django if it > doesn't. A new rule type implementing this sort of checking arrived at trunk yesterday. You can either wait a few weeks to get the new release, or run trunk. For what is worth, we don't plan to make huge changes in the upcoming release, so it should be almost as stable as the stable branch. > I can see two ways to go about this: > > 1) Putting Django under a SCGI Handler in a /django/ directory rule, > and > then setting /django/ (in addition to index.html) as the directory > index for the List&Send handler. Except it doesn't work: the L&S > handler returns a directory listing instead of calling Django. Did I > misunderstand the documentation, where it speaks about using > e.g. /cgi-bin/index.pl as a directory index? > > 2) Adding an option to the L&S Handler (or to all of them, really) so > that in case there's no file matching the request (i.e., the Handler > would return a 404, or a directory listing in the case of L&S), they > can pass it down to the next handler. > > The second option would be far better but does require some > implementation work in Cherokee. Unless this is already possible and I > didn't find how? Well, with trunk you can now set rules that check whether a file is present in your documentroot, so you can be served in case it exists. If the file weren't exist, the rule wouldn't match, and the request would be handled by another rule. In this case, the default Djando rule (scgi/fastcgi) would likely be used. > Lastly, I rent a virtual server on which there is no loopback > interface, > making the use of the 127.0.0.1 address to secure the admin interface > impossible. Is there, or will there be a way to lock the interface > behind a password (and if at all possible, SSL)? I'm not sure I'm getting it. These are the two cases I can imagine: - As long as cherokee-admin binds to lo, you cannot access it remotely. It's a server, so you don't have X Window installed, so you cannot run a browser and export the Xsession either. In this case the easiest work-around would be to forward the 9090 port with SSH. In that way, you could map it in your local box and use your browser to access it: http://blogs.sun.com/alvaro/entry/administrating_remote_cherokee_servers - The second case would be that, by some reason, cherokee-admin cannot access the loop interface. That'd be really weird. Actually, I haven't been able to figure out how we could deal with such a bizarre set up. -- Octality http://www.octality.com/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
