[rt-users] Dev & Prod RT

[joby]

I strongly recommend using some sort of version control.  Our RT 
installation is the combination of 8 separate projects stored within an 
SVN repository:

1) rt/bp: the best practical RT distribution + some RTx extensions.
2) rt/cac/html: the local/html directory
3) rt/cac/lib: the local/lib directory
4) rt/conf/status: config directives for development level (Develmode)
5) rt/conf/db: config directives for database connection
6) rt/conf/base: remaining configuration directives
7) rt/bin: some management scripts (mostly run from cron).
8) rt/perl: the perl installation that rt uses

Then our milestones are a combination of specific releases of each 
project.  Being able to easily revert to a previous milestone has saved 
our ass a couple times.

jbw

Toby Darling wrote:
> Hi
> 
>>> My bigger concern is when i go to add things to the interface, or
>>> generally muck around in RT :)
>>
>> The Interface stuff tends to be editing files in /opt/rt3/local so your
>> rsync should work there.
>> http://wiki.bestpractical.com/index.cgi?CleanlyCustomizeRT
> 
> I've been using plain old scp between dev and prod, mainly because 
> there's usually other stuff in dev that isn't ready for prod just yet.
> 
> We're now looking at going to 3.6.x and I'm thinking about changing this 
> and using CVS - commit on dev, update on prod; and it would also give a 
> nice trail of how files change over time (there's one file that's had 3 
> edits for 3 separate tweaks, but 6 months down the line and I'm having 
> trouble figuring what's doing what). Any thoughts?
> 
> Cheers
> Toby
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
> 
> Community help: http://wiki.bestpractical.com
> Commercial support: sales at bestpractical.com
> 
> 
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy 
> a copy at http://rtbook.bestpractical.com