Re: [Resin-interest] Is there an easy way to do this? port
Jose Quinteiro escribió: Hi, 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. Cheers! D. 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. HTH, Jose. Vinny wrote: Hi, I am trying figure out a way to do a kind of virtual hosting based on port number. 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 like 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 resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Is there an easy way to do this? port
On Feb 2, 2007, at 12:39 AM, Daniel López wrote: Jose Quinteiro escribió: Hi, 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. True. 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. FYI, in Resin 3.1 you could just use one config file and have two separate cluster blocks. The -server foo will select which cluster will be active for that JVM. -- Scott 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. Cheers! D. 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. HTH, Jose. Vinny wrote: Hi, I am trying figure out a way to do a kind of virtual hosting based on port number. 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 like 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 resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] Is there an easy way to do this? port
Hi, I am trying figure out a way to do a kind of virtual hosting based on port number. 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 like I will have to make a completely seperate server/ block? Is that really the case? Thanks in advance -- Ghetto Java: http://www.ghettojava.com ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Is there an easy way to do this? port
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. HTH, Jose. Vinny wrote: Hi, I am trying figure out a way to do a kind of virtual hosting based on port number. 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 like 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 resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Is there an easy way to do this? port
On Feb 1, 2007, at 9:35 AM, Vinny wrote: Hi, I am trying figure out a way to do a kind of virtual hosting based on port number. 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. You can just add the port to the virtual host: host id=foo.com:8080 root-directorydev/root-directory ... /host host id=foo.com root-directoryproduction/root-directory ... /host -- Scott I was thinking perhaps I could nest host/ under http/ but it seems like I will have to make a completely seperate server/ block? Is that really the case? Thanks in advance -- Ghetto Java: http://www.ghettojava.com ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest