right now we do a lot of if production then sorta logic, but it'd probably be more flexible to read from config what to do, and to set the enable/disable flags in env-specific overrides
Rather than generate all these in the blueprint project, doing the same sorta dance where config/development exists in both cabbage and user dirs with users free to override seems to make the most sense.
One clear cut example of this would be:
js:
uglify:
enabled: true
In config/production, but false in config/development and config/test
right now we do a lot of
if production thensorta logic, but it'd probably be more flexible to read fromconfigwhat to do, and to set the enable/disable flags in env-specific overridesRather than generate all these in the blueprint project, doing the same sorta dance where
config/developmentexists in both cabbage and user dirs with users free to override seems to make the most sense.One clear cut example of this would be:
In config/production, but false in config/development and config/test