[Rt-devel] A new design question

[Todd Chapman]

On Mon, Mar 21, 2005 at 03:28:44PM -0300, Lucas F. Rosada wrote:
>    What is the possibility and the impact of developing a new kind of 
> customization system to RT, where each queue or other bigger unit is a 
> directory and, inside each directory, we have sub-directories for custom 
> fields, scripts, templates, etc.
>    Doing the thing in this way the database will be really a data 
> repository and the code will be only into the files.
> 
> Follow an example direcotry structure:
> 
> + Customizations
> + Queues
>  - DelegatedRights.cfg
>  + Scrips
>   - scrip1.scp
>   - scrip2.scp ...
>  + Templates
>   - template1.tmpl
>   - template2.tmpl ...
>  + Custom Fields
>   - CF1.cf
>   - CF2.cf
> + Global
>  - DelegatedRights.cfg
>  + Scrips
>   - scrip1.scp
>   - scrip2.scp ...
>  + Templates
>   - template1.tmpl
>   - template2.tmpl ...
>  + Custom Fields
>   - CF1.cf
>   - CF2.cf
>  + Users
>   - user1.usr
>   - user2.usr
>   - user3.usr
>  + Groups
>   - group1.grp
>   - group2.grp
> 
> This is a little idea. I felt the dificult of transport the code (local 
> directory) and the scrips, etc from the development server to the 
> production server, where I had to dump the database without touching the 
> tickets and other vital data of the customer. Maybe leaving the code in 
> the files, inside the RT directory structure, would be a nice start.
> 
> Does anyone have an idea of the impact or how to refine this scructure?

The only problem you mention with the current system is the work
it takes to move customizations from development to production.

I think it would be better to develop code that uses the API to
make this easier than to redesign RT.

-Todd