I would extend the built-in resource plugin so that it accepts a "configPath" option that points to an external config file. Once the external config is loaded, you can call parent::init() and continue on like normal.
-- *Hector Virgen* Sr. Web Developer Walt Disney Parks and Resorts Online http://www.virgentech.com On Tue, Oct 26, 2010 at 9:01 AM, Frank DiRocco <ofang...@gmail.com> wrote: > Henry, > > Have you tried loading the config? I do something like this in my 1.10.x > bootstrap _inits, the ini file is compiled just like application.ini > > $config = new Zend_Config_Ini('path/to/yourDbSchemaCredentials.ini', > 'dbsecrets'); > > Just keep in mind, your credentials will be available/accessible in this > $config variable > > On Oct 26, 2010, at 9:10 AM, Henry Umansky wrote: > > > Hello all, > > I'm trying to upgrade my pre-1.8 ZF application to the latest version and > utilize Zend_Application. However, I'm running into a subversion security > issue. Within my old application, I was able to store my database connection > information into a separate config.ini file and then simply add that file to > the svn:ignore list. That way my sensitive database information is not > stored in my public subversion repository. However, now that I'm using > Zend_Application, I can't really add application.ini to the svn:ignore list > (nor do I want to, since I use Capistrano for deployment). Is there a "best > practice" for scenarios similar to this? Can I add another config file in > something like a _initDB() in the Bootstrap.php file or is there another > recommended method? > > > > Thank you, > > Henry > >
