Re: seperate development spaces on same server/tomcat
On Tue, Sep 21, 2004 at 04:59:42PM +, Didier McGillis wrote: : to setup up three instances of the same site. Here is the reason. I have : three developers who are coming in. I have one set of code, rather then : they share it, and play that way I would rather them have their own spots : to play. : [snip] : so HTML/images is in /usrl/local/apache2/guy1, guy2, guy3 : jsp/java/servlets is in /usr/local/tomcat/webapps/guy1, guy2, guy3 : : http://server/guy1 : http://server/guy1 : http://server/guy3 Check out the Tomcat docs on CATALINA_BASE vs CATALINA_HOME, which lets you provide each developer with their own Tomcat instance (separate JVMs). Find/create custom scripts for each developer to start/stop their own instance. The rest is, well, up to the developers. They should be able to check out the entire site from source code control (or however it's stored). They would work on just their piece, and only check-in code related to their piece; but to be effective, they should be able to run/see the full site within their instance. Taking this a step farther, you could create another instance for QA, one for load-tests, etc. -QM -- software -- http://www.brandxdev.net tech news -- http://www.RoarNetworX.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: seperate development spaces on same server/tomcat
Thanks. I'm still a little fuzzy on the Apache part. Do I point Apache to the the context, or do I point it to a folder. I would rather keep HTML/images out of the java/jsp space, however this is a pre existing site with alot of static HTML pages with preexisting links to the jsp pages. From: QM <[EMAIL PROTECTED]> Reply-To: "Tomcat Users List" <[EMAIL PROTECTED]> To: Tomcat Users List <[EMAIL PROTECTED]> Subject: Re: seperate development spaces on same server/tomcat Date: Tue, 21 Sep 2004 12:08:12 -0500 On Tue, Sep 21, 2004 at 04:59:42PM +, Didier McGillis wrote: : to setup up three instances of the same site. Here is the reason. I have : three developers who are coming in. I have one set of code, rather then : they share it, and play that way I would rather them have their own spots : to play. : [snip] : so HTML/images is in /usrl/local/apache2/guy1, guy2, guy3 : jsp/java/servlets is in /usr/local/tomcat/webapps/guy1, guy2, guy3 : : http://server/guy1 : http://server/guy1 : http://server/guy3 Check out the Tomcat docs on CATALINA_BASE vs CATALINA_HOME, which lets you provide each developer with their own Tomcat instance (separate JVMs). Find/create custom scripts for each developer to start/stop their own instance. The rest is, well, up to the developers. They should be able to check out the entire site from source code control (or however it's stored). They would work on just their piece, and only check-in code related to their piece; but to be effective, they should be able to run/see the full site within their instance. Taking this a step farther, you could create another instance for QA, one for load-tests, etc. -QM -- software -- http://www.brandxdev.net tech news -- http://www.RoarNetworX.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Take charge with a pop-up guard built on patented Microsoft® SmartScreen Technology. http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines Start enjoying all the benefits of MSN® Premium right now and get the first two months FREE*. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: seperate development spaces on same server/tomcat
Hi, For development, drop Apache httpd, drop the connectors, drop the notion of CATALINA_BASE. Simply install Tomcat x separate times to x separate directories, with nothing in common. That's it. Yoav Shapira Millennium Research Informatics >-Original Message- >From: Didier McGillis [mailto:[EMAIL PROTECTED] >Sent: Tuesday, September 21, 2004 1:57 PM >To: [EMAIL PROTECTED] >Subject: Re: seperate development spaces on same server/tomcat > >Thanks. > >I'm still a little fuzzy on the Apache part. Do I point Apache to the the >context, or do I point it to a folder. I would rather keep HTML/images out >of the java/jsp space, however this is a pre existing site with alot of >static HTML pages with preexisting links to the jsp pages. > > > > >>From: QM <[EMAIL PROTECTED]> >>Reply-To: "Tomcat Users List" <[EMAIL PROTECTED]> >>To: Tomcat Users List <[EMAIL PROTECTED]> >>Subject: Re: seperate development spaces on same server/tomcat >>Date: Tue, 21 Sep 2004 12:08:12 -0500 >> >>On Tue, Sep 21, 2004 at 04:59:42PM +, Didier McGillis wrote: >>: to setup up three instances of the same site. Here is the reason. I >>have >>: three developers who are coming in. I have one set of code, rather then >>: they share it, and play that way I would rather them have their own >spots >>: to play. >>: [snip] >>: so HTML/images is in /usrl/local/apache2/guy1, guy2, guy3 >>: jsp/java/servlets is in /usr/local/tomcat/webapps/guy1, guy2, guy3 >>: >>: http://server/guy1 >>: http://server/guy1 >>: http://server/guy3 >> >>Check out the Tomcat docs on CATALINA_BASE vs CATALINA_HOME, which lets >>you provide each developer with their own Tomcat instance (separate >>JVMs). Find/create custom scripts for each developer to start/stop >>their own instance. >> >>The rest is, well, up to the developers. They should be able to check >>out the entire site from source code control (or however it's stored). >>They would work on just their piece, and only check-in code related to >>their piece; but to be effective, they should be able to run/see the >>full site within their instance. >> >>Taking this a step farther, you could create another instance for QA, >>one for load-tests, etc. >> >>-QM >> >>-- >> >>software -- http://www.brandxdev.net >>tech news -- http://www.RoarNetworX.com >> >> >>- >>To unsubscribe, e-mail: [EMAIL PROTECTED] >>For additional commands, e-mail: [EMAIL PROTECTED] >> > >_ >Take charge with a pop-up guard built on patented Microsoft(r) SmartScreen >Technology. >http://join.msn.com/?pgmarket=en- >ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Mark et_M >SNIS_Taglines > Start enjoying all the benefits of MSN(r) Premium right now and get the >first two months FREE*. > > >- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: seperate development spaces on same server/tomcat
On Tue, Sep 21, 2004 at 02:10:42PM -0400, Shapira, Yoav wrote: > For development, drop Apache httpd, drop the connectors, drop the notion > of CATALINA_BASE. Simply install Tomcat x separate times to x separate > directories, with nothing in common. That's it. or, if your developers can deal with not restarting tomcat all the time (or notifying the others when they do), then you can just install you app to a separate path within a single tomcat instance and save the overhead of extra tomcat instances. If you're using the ant deploy task, it would look something like this: http://${tomcaturl}/manager"; username="${manager_username}" password="${password}" path="/yourapp.${username}" war="yourapp.war"/> You just have to give the developers access to the user that is running tomcat. I have a script that uses sudo to restart it when needed. It works reasonably well. eric - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: seperate development spaces on same server/tomcat
Didier, if you want to use apache, and all the fixins, search the list back about a week for a post i made...it has all of the info you need to set this up. Uses apache and tomcat with virtual hosts ... or iis . A simpler solution is get them to have an install of tomcat for each of them as Yoav suggested. On Tue, 21 Sep 2004, Shapira, Yoav wrote: > Date: Tue, 21 Sep 2004 14:10:42 -0400 > From: "Shapira, Yoav" <[EMAIL PROTECTED]> > Reply-To: Tomcat Users List <[EMAIL PROTECTED]> > To: Tomcat Users List <[EMAIL PROTECTED]> > Subject: RE: seperate development spaces on same server/tomcat > > > Hi, > For development, drop Apache httpd, drop the connectors, drop the notion > of CATALINA_BASE. Simply install Tomcat x separate times to x separate > directories, with nothing in common. That's it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: seperate development spaces on same server/tomcat
Why is Tomcat serving the error pages? I try to go to catalog2.html which I know doesnt exist and I get the Tomcat error page, however in the Apache logs there is the log of me requesting catalog2.html. I know it must have something to do with my workers2.properties setting have the uri:/* set From: [EMAIL PROTECTED] Reply-To: "Tomcat Users List" <[EMAIL PROTECTED]> To: Tomcat Users List <[EMAIL PROTECTED]> Subject: Re: seperate development spaces on same server/tomcat Date: Tue, 21 Sep 2004 15:44:07 -0500 On Tue, Sep 21, 2004 at 02:10:42PM -0400, Shapira, Yoav wrote: > For development, drop Apache httpd, drop the connectors, drop the notion > of CATALINA_BASE. Simply install Tomcat x separate times to x separate > directories, with nothing in common. That's it. or, if your developers can deal with not restarting tomcat all the time (or notifying the others when they do), then you can just install you app to a separate path within a single tomcat instance and save the overhead of extra tomcat instances. If you're using the ant deploy task, it would look something like this: http://${tomcaturl}/manager"; username="${manager_username}" password="${password}" path="/yourapp.${username}" war="yourapp.war"/> You just have to give the developers access to the user that is running tomcat. I have a script that uses sudo to restart it when needed. It works reasonably well. eric - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Powerful Parental Controls Let your child discover the best the Internet has to offer. http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines Start enjoying all the benefits of MSN® Premium right now and get the first two months FREE*. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]