If it can be in the config.php, I like to see it in the config.php.sample.
That's the purpose.  If config options have moved to the db and are
controllable from an admin web interface, that's fine and dandy, too.

I'm guessing that I'll never use the install program.  I'm already installed
and all I need to do is upgrade - merge your new upstream code into mine,
adjust config (sample comes in handy), test, and deploy.  Don't forget the
code tweaks between each step :).

So, unless the install program will tell me "Hey, these are the enw config
options that have appeared between your last install and this one, would you
like to enable/set them" and walk me through it, I wouldn't have a use for
it.  And even then, manual settings are more likely for me because I have
sets of custom config options in my install as well.

Just one man's opinion.

-- 
Mark
"Blessed is he who finds happiness in his own foolishness, for he will
always be happy."


On Mon, Dec 14, 2009 at 1:12 PM, Evan Prodromou <e...@status.net> wrote:

> So, we have a template for config.php in the current distribution.
>
> Our (default) config.php files become much small in 0.9.x, since we're
> storing (most) configuration info in the database now. We've also got a
> Web-based administrative interface, so figuring out config options is less
> of an issue.
>
> It's been hard for us to keep the canonical config options in the README
> and the config.php.sample file up-to-date.
>
> I'd like to therefore remove the config.php.sample file entirely, and
> recommend that people use the install program instead.
>
> Any objections?
>
> -Evan
>
> --
> Evan Prodromou
> CEO, StatusNet, Inc.
> e...@status.net - http://identi.ca/evan - +1-514-554-3826
>
> _______________________________________________
> StatusNet-dev mailing list
> StatusNet-dev@lists.status.net
> http://lists.status.net/mailman/listinfo/statusnet-dev
>
_______________________________________________
StatusNet-dev mailing list
StatusNet-dev@lists.status.net
http://lists.status.net/mailman/listinfo/statusnet-dev

Reply via email to