>--===============1115171146== >Content-Type: multipart/alternative; > boundary="----=_Part_8390_1032883.1199978446926" > >------=_Part_8390_1032883.1199978446926 >Content-Type: text/plain; charset=UTF-8 >Content-Transfer-Encoding: 7bit >Content-Disposition: inline > >I have had to think about this a lot. Maintaining one RT with customizations >for lots of different groups can be challenging. Maintaining multiple RT >instances and trying to keep some customizations in sync across those >instances can also be a bit of a pain. > >So what it comes down to for me is risk. I can't have my externally facing >customer service queues being screwed up by customization for my internal >queues. So for me customer service gets its own instance and everyone else >gets another instance.
Interesting. For code customizations, I have my paths set up so that a given instance gets a base part (governing the core RT version), a common part for all instances (of that RT version) where I put _vendor files, and a per-instance part. Any customization I want to apply to all instances is easy, and I can still have per-instance differences. Of course, if you mean customizations in the RT config file or in the database, this doesn't help. bobg > >-Todd > >On 1/9/08, james machado <[EMAIL PROTECTED]> wrote: >> >> Hi All, >> >> My question is both hypothetical and practical. I've got RT deployed in >> my I.T. department doing what it does best and it's working well. I've >> put feelers out to some other departments that I think could benefit from RT >> to see if they would be interested in having it setup for them. I am finely >> getting some positive responses so I'm looking for some guidance on >> deployment options. I am trying to decide if I should share an instance of >> RT among 1+ departments or create a new instance of RT for each department. >> Hardware is not an issue either way, nor does it look like the traffic >> volume will be an issue. These are all internally created tickets with no >> Internet access to my RT instance. If Internet access were required then a >> separate instance of RT would be desirable. >> >> So what I am looking for from people who have either had this issue or >> thought about it is: what factors you would take into account when deciding >> on 1 or more instances of RT and why. >> >> Thanks, >> >> James >> >> _______________________________________________ >> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users >> >> Community help: http://wiki.bestpractical.com >> Commercial support: [EMAIL PROTECTED] >> >> >> Discover RT's hidden secrets with RT Essentials from O'Reilly Media. >> Buy a copy at http://rtbook.bestpractical.com >> > >------=_Part_8390_1032883.1199978446926 >Content-Type: text/html; charset=UTF-8 >Content-Transfer-Encoding: 7bit >Content-Disposition: inline > >I have had to think about this a lot. Maintaining one RT with customizations f >or lots of different groups can be challenging. Maintaining multiple RT instan >ces and trying to keep some customizations in sync across those instances can >also be a bit of a pain. ><br><br>So what it comes down to for me is risk. I can't have my externall >y facing customer service queues being screwed up by customization for my inte >rnal queues. So for me customer service gets its own instance and everyone els >e gets another instance. ><br><br>-Todd<br><br><div><span class="gmail_quote">On 1/9/08, <b class="gmail >_sendername">james machado</b> <<a href="mailto:[EMAIL PROTECTED]">hvge >[EMAIL PROTECTED]</a>> wrote:</span><blockquote class="gmail_quote" style=" >border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding- >left: 1ex;"> >Hi All,<br><br>My question is both hypothetical and practical. I've >got RT deployed in my I.T. department doing what it does best and it's wor >king well. I've put feelers out to some other departments that I thi >nk could benefit from RT to see if they would be interested in having it setup > for them. I am finely getting some positive responses so I'm lookin >g for some guidance on deployment options. I am trying to decide if I sh >ould share an instance of RT among 1+ departments or create a new instance of >RT for each department. Hardware is not an issue either way, nor does it > look like the traffic volume will be an issue. These are all internally > created tickets with no Internet access to my RT instance. If Internet >access were required then a separate instance of RT would be desirable. ><br><br>So what I am looking for from people who have either had this issue or > thought about it is: what factors you would take into account when deciding o >n 1 or more instances of RT and why.<br><br>Thanks,<br><span class="sg"> ><br>James<br> ></span><br>_______________________________________________<br><a onclick="retu >rn top.js.OpenExtLink(window,event,this)" href="http://lists.bestpractical.com >/cgi-bin/mailman/listinfo/rt-users" target="_blank">http://lists.bestpractical >.com/cgi-bin/mailman/listinfo/rt-users ></a><br><br>Community help: <a onclick="return top.js.OpenExtLink(window,event >,this)" href="http://wiki.bestpractical.com"; target="_blank">http://wiki.bestp >ractical.com</a><br>Commercial support: <a onclick="return top.js.OpenExtLink( >window,event,this)" href="mailto:[EMAIL PROTECTED]"> >[EMAIL PROTECTED]</a><br><br><br>Discover RT's hidden secrets with R >T Essentials from O'Reilly Media.<br>Buy a copy at <a onclick="return top. >js.OpenExtLink(window,event,this)" href="http://rtbook.bestpractical.com"; targ >et="_blank"> >http://rtbook.bestpractical.com</a><br></blockquote></div><br> > >------=_Part_8390_1032883.1199978446926-- > >--===============1115171146== >Content-Type: text/plain; charset="us-ascii" >MIME-Version: 1.0 >Content-Transfer-Encoding: 7bit >Content-Disposition: inline > >_______________________________________________ >http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users > >Community help: http://wiki.bestpractical.com >Commercial support: [EMAIL PROTECTED] > > >Discover RT's hidden secrets with RT Essentials from O'Reilly Media. >Buy a copy at http://rtbook.bestpractical.com >--===============1115171146==-- > _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
