Jose Quinteiro escribió:
As Jose, I would recommend having different instances for development
and deployment. Even though Resin does a good job on separating contexts
and detecting changes and restarting just the appropriate web app. You
will still affect your deployment applications with the common frequent
restarts during development.
And as Jose said, you don't need two copies of the whole Resin software,
just two config files so you don't have to worry about
maintaing/upgrading two full instances.
In fact, we use more than one instance even in deployment, as that
allows us to handle upgrades/problems more gracefully as applications
affected by what happens to others is minimised.
> The way I've accomplished this is by having two different instances of
> Resin, with different conf files. It's easy to do with 3.0.x, a little
> harder with 3.1.0.
> Vinny wrote:
>>I am trying figure out a way to do a kind of virtual hosting based on
>>I want my production apps running under port 443
>>docroot : (/web/production/webapps)
>>and my dev apps running under 8080.
>>docroot : (/web/dev/webapps)
>>both production and dev apps will have the same context
>>names (like ROOT.war for example) I just need resin to differentiate
>>on port number basically.
>>I was thinking perhaps I could nest <host/> under <http/> but it seems
>>I will have to make a completely seperate <server/> block?
>>Is that really the case?
>>Thanks in advance
>>Ghetto Java: http://www.ghettojava.com <http://www.ghettojava.com>
resin-interest mailing list