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
On Fri, 19 Jan 2007, Toby Darling wrote:
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
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
So i am setting up 2 machines, one will be my Dev machine and the other
the production.
If i start out with both machines equal then make changes to the dev
machine. To bring the production one current all I'd need to do is rsync
the /opt/rt3 directory to the prod machine?
Basically I'm
On Jan 18, 2007, at 2:44 PM, Ryan Hardester wrote:
Basically I'm making sure that what isn't in the DB is contained in
the /path/to/rt3 folder. I'm pretty sure, just wanted to make sure
before i commit to this setup :)
what exactly are you attempting to do? prototype some changes then
If i start out with both machines equal then make changes to the dev
machine. To bring the production one current all I'd need to do is
rsync
the /opt/rt3 directory to the prod machine?
Basically I'm making sure that what isn't in the DB is contained in
the /path/to/rt3 folder. I'm pretty
Even if you could bring over custom fields, you'd have to create them in
the exact same order on both machines because each one has a number that
is used internally to identify it.
Scott Golby wrote:
If i start out with both machines equal then make changes to the dev
machine. To bring the
Well right now I am running 3.6.1 on prod and my new dev is 3.6.3 and
accessing the old database. I'm assuming this works because there are no
major changes. When I move the 3.6.3 to prod i'll update the database.
My bigger concern is when i go to add things to the interface, or
generally muck
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
For the 'general mucking around' I've
