asset_compress.ini has two kinds of config

[HaroldPutman]

We are running into trouble where the same asset_compress.ini is used in different evironments. So the sattings like the paths to tools like uglify and Less are mixed in with the definitions of the targets.

Our developers are running on Windows, Mac, and Linux which all need different values for the paths of these tools, but all need the same target definitions.

We solve this by having an asset_compress.ini.template that we use to generate asset_compress.ini files specific for each environment. The problem is that I have to remember to move the target definition changes into this template from my local asset_compress.ini.

I couldn't see any obvious workaround, but would it make sense to separate out the two kinds of configuration? Maybe putting the paths and stuff in different config file? Or is there a way to shove this config in a runtime after the plugin is loaded?

[markstory]

Either two kinds of configuration, or merging the results of two configuration files seems like a solution to this. I generally solve the platform issues with virtual machines, as it helps solve a host of other issues caused by developing on a different platform/OS than you are deploying to.

[Codaxis]

Should be closed, #198 adds support for per environment config.