[Catalyst] Suggestions for CatalystX::Installer

[Kieren Diment]

On 14 May 2008, at 18:43, Andreas Marienborg wrote:
>
> I would say that making sure the deps are correct would not be the  
> job of CatalystX::Installer, but the developer of the app.
>

Yes, but it's useful ^W essential to let the dev team know when  
they've stuffed up.


> What I hope CatalystX::Installer will be, is something that I can  
> use in my apps to make them easier to set up for people installing  
> the app.
>
> This for me includes:
>
> - dependency handling
> any deps the app needs, that isn't available, or the wrong version  
> should be installed / helped installed. For instance, a debian user  
> might want suggestions for debian packages to install (quite large  
> scope :p) For me it should not infer deps automaticly at this time,  
> that the developer should do before releasing his app.
>

yep, local:lib or par i'm not sure which.  Someone else can answer  
this one.


> - app configuration
> Databases, paths, etc. This needs to be very customizable/ 
> pluggable. For instance in easycms2, I have a config setting for  
> what resizes to make of pictures. It would be classy if I could  
> easily map this to some webform using CatalystX::Installer :p
>

+1

> - schema deployment / upgrades
> Deploy or upgrade the given database-configuration. This sort of  
> infers that the CatalystX::Installer also can be used for upgrades :p
>


hmm, scope creep

> - example configurations
> For apache, lighty, nginx, perlbal(?), http-server, fastcgi etc.
> Perhaps it could even go as far as trying to put config under the  
> propper /etc/apache/conf-enabled or whatever (this becomes distro- 
> specific, and probably needs to be pluggable)
>

yep, sounds fine for a prototype

> - Running tests.
> This I think is a cool idea, to optionally run tests against the  
> finished setup. The author should perhaps specify which tests to run
>
>

and the name of the server to run them against.

> - andreas
>

Thanks for the input.