[jifty-devel] Re: [Jifty-commit] r2031 - wifty/trunk/etc

Henry Baragar Henry.Baragar at instantiated.ca
Thu Nov 2 11:12:54 EST 2006

On Thursday, November 02 2006 09:29 am, Jesse Vincent wrote:
> >
> > I propose that the following lines be added to the distributed
> > etc/config.yml file:
> >
> >   SiteConfig: etc/site_config.yml
> >   TestConfig: etc/test_config.yml
> >   VendorConfig: etc/vendor_config.yml
> >
> > That way, other Jifty newbies can avoid the couple of hours I spent
> > trying to figure out if this feature is present and how to use it.
> Rather than hardcoding it into the generated configuration file (You may
> have guessed by now that I don't like to hardcode things that fall
> through sanely, what about adding a comment to the generated
> configuration file with a pointer to the documentation?

A pointer to the documentation would be good.

Otherwise, I am confused about your comments...

Regarding "fall through sanely", what is the fall through?  I had interpreted 
that to mean that it would look for a site_config.yml file, even if there is 
no SiteConfig directive in config.yml.  My first reaction was that I must 
have done something wrong, like misspelling site_config.yml. However, the 
real reason was that site_config.yml was not found until I explicitly put the 
SiteConfig directive into config.yml.  

Regarding hardcoding, what is being hardcoded?  SiteConfig is hardcoded in 
Jifty::Config.  And, nothing bad happens if etc/site_config.yml does not 
exist.  Maybe, my confusion of the hardcoding is due to my confusion about 
"fall through sanely".


> Best,
> Jesse
> > Regards,
> > Henry
> >

More information about the jifty-devel mailing list