Menu

#2 configuration

open
nobody
None
5
2005-02-02
2005-01-28
Dan
No

We need to decide on an easy configuration system. I
suggest PEAR::Config is given a good hard look at. This
is because your paths are not my paths.

Additionally, installer needs to check these things and
warn the end user if misconfigurations are made
*before* they get anywhere near loader.php
just-not-working.

Discussion

  • chris were

    chris were - 2005-02-01

    Logged In: YES
    user_id=1177807

    Yep you're right. I've gone through about 3 different
    loading mechanisms while working on the framework - finally
    settling on the one released. As a result the config is
    fairly messy - I'll have a look at PEAR::Config. It should
    be posssible to make the configuration quite simple.

     
  • chris were

    chris were - 2005-02-01
    • status: open --> pending
     
  • Dan

    Dan - 2005-02-02
    • status: pending --> open
     
  • Dan

    Dan - 2005-02-02

    Logged In: YES
    user_id=197121

    Also, don't forget to have some way of locally overriding
    the default configuration that we won't destroy during CVS
    checkouts... it's getting annoying to find all the of the
    /var/www/qwadframeworks and put in the right details :/ -
    ie, config.php + config.local.php

     

Log in to post a comment.