Closed amleczko closed 11 years ago
I would prefer to keep the old approach because:
It seems to me more complicate rather than simple... just my 2c!
_base.cfg
convention is just a proposal - it can be of course kept without _
.I see your point, especially the mess part :) What about creating two folders:
New update:
./profiles
we can keep top level cfgs (development, production, etc)./config
we can keep the rest (plone, base, etc)Ok for me!
I would like to propose a similar but more simple approach:
./config/
I would suggest to use a convention that everything that starts with_
shouldn't be used as a starting configuration (aka symlinked in root)development.cfg
should be only (one file that has all the dev sections)