-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple configuration files #264
Comments
Does the |
I haven't found any reference to that option in the wiki. |
Its in the help for the cli tool. I'll add it to the wiki as well. |
Right. I see it now. But yeah, it would be nice having it in the wiki as well. |
I've seen that if I have two config files and none of them has the default name
Does it means I have to create an empty file with the name |
I updated the wiki for the command line flag. Yes, the plugin assumes and expects you have a config file with the default name. I don't think anyone has earnestly wanted to use multiple config files before. |
In that case, does it matter at all which of the config files is as the default one? Will it have any consequences on the page? |
Telling the various parts of the plugin which is 'default' is the only challenging thing I think. |
It would be nice to be able to define different configuration files.
In my case, I have a website and then an application inside it. It would be ideal to be able to separate both sites, as they don't have any single javascript file in common.
Right now I'm compressing it using:
It seems to me a nice solution to be able to specify another string instead of
build_ini
with the name of the configuration file insideapp/config
.The text was updated successfully, but these errors were encountered: