The separate installer script is a good idea, but I'd stick with a single
ini configuration file. The installer script doesn't need to bootstrap
everything like your application does. You can pick and choose what to
bootstrap:
$application = new Zend_Application(APPLICATION_ENV, APPLICATION_PATH .
'/configs/application.ini');
$bootstrap = $application->getBootstrap();
$bootstrap->bootstrap('frontcontroller');
$bootstrap->bootstrap('view');
$bootstrap->bootstrap('router');
$application->run();
--
*Hector Virgen*
Sr. Web Developer
Walt Disney Parks and Resorts Online
http://www.virgentech.com
On Thu, Sep 30, 2010 at 7:46 AM, Daniel Stefaniuk <
daniel.stefan...@gmail.com> wrote:
> I have build an installer for my web application and I have a problem when
> the bootstrap process initializes all the resources defined in the
> application.ini file. Because a database haven't been created yet some of
> the resources that need to use it fail to initialize.
>
> I created two application's entries, main one (index.php) and one for the
> installer (install.php) along with their own bootstraps and configuration
> files. But now, this forces me to maintain duplicated properties (in
> application.ini and install.ini files) defined for both bootstrap
> processes.
> The list is pretty big as I declare a lot of custom properties I need to
> have access to during normal application usage and installation.
> Personally,
> I don't like this solution.
>
> What is the best approach to solve this problem?
>
> Thanks
>
> Daniel
>
