Ax2 production setup

2007-01-10 Thread john1
Lo all,

I'm running it on RH Linux.

Currently I have one app set up thus:

/var/www/AxKit2/APP_1

AxKit2 contains the axkit prog and a link to the plugins directory.
APP_1 contains
./web
./web/plugins
./web/stylesheets
./web/webroot
./web/webroot/graphics
./web/webroot/js

Now it's been mentioned before to use daemontools, so I can set 
that up. Is daemontools the way to go? I am more used to an rc.foo
script.

Given that there will be two other apps (at least), should I have one
Ax2 server or one for each app? I am leaning towards one for each 
app because we have 4 cpus and I presume it would be better for 
throughput.

TIA

John


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Ax2 production setup

2007-01-10 Thread Matt Sergeant

On 10-Jan-07, at 4:52 AM, [EMAIL PROTECTED] wrote:


Now it's been mentioned before to use daemontools, so I can set
that up. Is daemontools the way to go? I am more used to an rc.foo
script.


I've seen qpsmtpd (which is very similar to AxKit2) be setup both  
ways. Probably preferable over daemontools is runit. See http:// 
wiki.qpsmtpd.org/deploy:runit for details.


We don't have a .rc file for AxKit2, but it should be easy enough to  
write one.



Given that there will be two other apps (at least), should I have one
Ax2 server or one for each app? I am leaning towards one for each
app because we have 4 cpus and I presume it would be better for
throughput.


I'd say multiple servers would be best then, yes.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]