We are also using separate instance of orion servers for different developers on the
same machine. However, people need to restart the server every time they upload the
classes to the testing machine and they always kill the wrong instance of orion
server. They are using "ps-Af|grep orion" and kill all the orion process.
Is there any better way to kill the orion server? If you have different instance of
orion servers on the same machine?
Also, is there any mailing list talking about web architecture? Like,
1. is 2 P500 CPU is better than 1 P733 CPU
2. Should I use NT to host orion or linux to host orion? It is because NT has a faster
VM (about 20-30% faster than linux VM??)
3. What is the deployment layout? Should I use RedHat LVS (Load balancing service) or
should I use the orion load balancing service?
4. should I put the mysql database on the same machine as the orion server or should I
put it in different machine?
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Lorin
> Kobashigawa
> Sent: Saturday, July 29, 2000 3:19 AM
> To: Orion-Interest
> Cc: Orion-Interest
> Subject: Re: Multiple developers with Orion
>
>
> Hey rick,
>
> We also have multiple developers working on the same box. We have given
> everyone an instance of Orion for their home directories, and use CVS to
> manage the applications. Our buildmaster/IS guy is in charge of managing
> the server.xml and default-web-site.xml files, and making they are all the
> same, and giving everyone unique ports.
>
> It's working very well so far, we initially tried a bunch of complicated
> setups with virtual hosts, and everyone having different applications, but
> it got very confusing very quickly, and we realized that separate
> instances
> were a lot better.
>
> -Lkb
>
> At 04:28 PM 7/28/00 +0200, Thomas Munro wrote:
> >Rick,
> >
> >Each of our developers has a seperate Orion instance running on their own
> >machine so they can bring it up and down whenever they want, and we are
> >using CVS to manage the sources. This seems to work reasonably well. We
> >share the same Oracle database, which occasionally causes problems when
> >someone changes something too much there, but most of the time it works
> >well.
> >
> >--
> >Thomas Munro <[EMAIL PROTECTED]>
> > http://www.gi-technology.com/
> > GI Technology (Paris)
> >
> >On Fri, 28 Jul 2000, Rick Bos wrote:
> >
> >> We have several developers working with Orion at the same time.
> >>
> >> We currently have a single instance of Orion which must be
> >> restarted when changes are made.
> >>
> >> Each user has a separate application that points to their working
> directory.
> >>
> >> Each user has a separate web location:
> >>
> >>
> >> /server/user1/Intro.jsp
> >> /server/user2/Intro.jsp
> >>
> >>
> >>
> >>
> >> Would it be a good idea to have multiple instances or Orion ?
> >> What would be the best way to do this ?
> >>
> >> Rick
> >>
> >>
> >
> >
> >
> /**
> * @author: Lorin Kobashigawa-Bates <[EMAIL PROTECTED]>
> * @title: CodeMonkey / COO - Robot6 Inc.
> * @phone: 415.345.8872
> * @addr: 1177 Polk St. San Francisco, CA 94109
> */
