On Monday, 28. August 2006 09:36, Lars Skjærlund wrote: > But what about virtual hosting? I run a webhotel based on AxKit with a > lot of virtual servers: With your new architecture, wouldn't that mean > running a lot of AxKit servers on different ports, one for each virtual > server? And then proxying through Apache in order to get them all back > at port 80 - or am I missing something here? I wouldn't describe this as > a simpler setup...
Well, we don't have it yet, but a very basic vhost plugin would be about 20 lines of code. If I am bored, I may even write it myself. And there are multiple <server> sections possible in the config, so Matt has probably thought of vhosting already, just some connecting bits are missing. It's really easy to hack on AxKit, check out the docs, AxKit2::WritingPlugins is a good starting point. > On the other hand I like the idea (and simplicity) of beeing able to > run AxKit standalone: But like Tomcat, maybe we should have both > options? It has been discussed to use a scheme like pperl, with a small CGI/mod_perl forwarder that starts AxKit2 if not yet running so it would "feel" like a single server. Should be easy to do, since others did these things already, and we are talking open source ;) > By the way, we're running SuSE Linux and at least with that distro, > installing Apache and mod_perl is simply a few clicks with the mouse and > you're up and running; it's a long time since I thought installing > mod_perl was any hassle at all ;-). The new AxKit2 architecture seems to > be a lot more complicated to me - at least when you need some of the > more fancy Apache options. Well, AxKit2 only has pure perl dependencies except for XML::LibXML (which is quite common nowadays), so setting it up is extremely simple. Nothing to compile, it "just works". "perl Makefile.PL; make; ./axkit" and you have a running AxKit2 demo server. You could even upload AxKit2 including all dependencies via FTP on you el-cheapo 100Meg webspace-with-perl and run it there. -- CU Moe --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
