falcone at bestpractical
Aug 4, 2009, 9:39 AM
Post #4 of 5
(1151 views)
Permalink
|
|
Re: advice on scrip development and deployment
[In reply to]
|
|
On Tue, Aug 04, 2009 at 08:33:13AM -0400, Andrew Libby wrote:
>
> I'm pretty sure scrips can be put in the database, but don't
> need to be. In either case they are registered in the
> database, at least the actions are. The ScripActions I'm
> using are growing in complexity, and as such I've taken them
> on to the filesystem.
Andy
You may want to look at Module::Install::RTx and build local RT
extensions that install your Actions. You can even write an
etc/initialdata to deploy the database pieces (look at the
initialdata that ships with RT for ideas)
You'll then enable your local extension with @Plugins, rather than
managing RT's @INC manually.
You can grab any of the modules on CPAN from one of the bps folks to
rip apart and get an idea of how to build one.
-kevin
>
> Jo Rhett wrote:
> > Scrips are in the database, not the filesystem, and survive upgrades
> > just fine.
> >
> > On Aug 3, 2009, at 6:27 PM, Andrew Libby wrote:
> >> I've hacked together a few scrips which are working pretty
> >> well. But I'd like to devise a method for managing my
> >> scrips in a way that survives upgrades well and does not
> >> interfere with the RT installation.
> >>
> >> I'm interested in hearing what folks are doing. I'm
> >> thinking of going about it like this:
> >>
> >> o Store my code in an SCM and deploy to it's own area
> >> on my system. Something like /opt/rt_company_scrips
> >> or the like.
> >>
> >> o Add the lib folder under the above mentioned directory
> >> to perls INC path via the apache configuration, or
> >> via some other method.
> >>
> >> o Add a company specific configuration file to a subfolder
> >> etc of the above mentioned path.
> >>
> >> Any thoughts on this? What are folks doing on this front?
> >>
> >> Thanks.
> >>
> >> Andy
> >>
> >> --
> >>
> >> ===============================================
> >> xforty technologies
> >> Andrew Libby
> >> alibby [at] xforty
> >> http://xforty.com
> >> ===============================================
> >>
> >> _______________________________________________
> >> List info:
> >> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel
> >
>
> --
>
> ===============================================
> xforty technologies
> Andrew Libby
> alibby [at] xforty
> http://xforty.com
> 610-761-1991
> ===============================================
>
> _______________________________________________
> List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel
>
_______________________________________________
List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel
|
