Re: Tux and multiple webservers?

Well I want to be able to use tux to serve the static content
from all these instances. The best way I can think to do this now
is to just btie the bullet and change all the references in the
code for the static content I want cached to go to a dns name
of static.sitename.com/images/blah.gif and mirror the directory
structure on another se rver we have spare.. hmm this is probably
a more scaleable solution in the long run, but it'd still
be nice to be able to associate seperate listening instances
with different server ports .. That'll probably be something that'll
appear around the time being able to make tux listen to webservers on
other boxes will.. 

= >What I really need is to have multiple instances of TUX, not just
= >tux listening on two ports.. We keep our app running in multiple
= >instances of apache, so when we have to push changes to a certain
= >instance, we don't have to restart the whole site, we can do it
= >one instance at a time.. so I need to say have tux listen on
= >port 8080 and pull data from apache on port 9080, as well as have
= >tux listen on port 8081 and pull data from apache port 9081, etc..
= >
= >Is there a way to do this?
= 
= I don't know.  I'm not sure I understand why you would want this.
= Tux is unlike Apache in many ways.  There's rarely a need to restart it (in 
= my experience, anyway).  It is optimized for serving files, so just change 
= the files and you're done, right?  no need to restart or run multiple instances.
= 
= 
= 
= _______________________________________________
= tux-list mailing list
= [email protected]
= https://listman.redhat.com/mailman/listinfo/tux-list
= 

-- 
---------------------------
Michael T. Halligan
Chief Geek
Halligan Infrastructure Designs.
2250 Jerrold Ave #11
San Francisco, CA 94124
(415) 824.4453