[dev] Install script ideas

[Jan Schneider]

Zitat von Barsalou <barjunk at attglobal.net>:

> I'd like to start some more conversation about an installation script.
> Below are some thoughts about how things might go.
>
> - The install script should install at least a very basic set of
> modules.  Currently they are:
>
> Horde
> Imp
> Ingo
> Kronolith
> Mnemo
> Nag
> Turba

I think the script should not consider anything. It should be generic enough
to install any module. It might be necessary to put a listing on the FTP
server that contains the available modules.

> - Horde will be setup to use MySql.

Wrong assumption.

> - The setup script will initially work from the command line:
>
>    php go-horde.php
>
> - Some ideas for a gui are here: http://bugs.horde.org/ticket/?id=82
>
> Additionally, there are a couple of different scripts available to
> install from HEAD.  Since the production versions are laid out
> differently, a alternate script is in the works.

IMO, the script first should bootstrap itself similarly to the go-pear
script by getting the necessary base classes from the CVS server via HTTP.
It should then check the system, similar to test.php (and probably using a
common set of test, no idea yet how to implement that though). If necessary
it should offer to install PEAR, necessary PEAR packages, and upgrade
existing PEAR packages.

After requesting the necessary information from the user it should download
and install the tarballs, create the configuration files, run SQL scripts.
It might be a good idea to run application-specific tasks by calling setup
scripts bundled with the applications.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/