Skip to content
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

Open
alvarotrigo opened this issue Apr 27, 2015 · 8 comments
Open

Multiple configuration files #264

alvarotrigo opened this issue Apr 27, 2015 · 8 comments

Comments

@alvarotrigo
Copy link

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:

cd C:\inetpub\wwwroot\cakephp\app
Console\cake AssetCompress.AssetCompress build_ini

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 inside app/config.

@markstory markstory added this to the 3.0 milestone Apr 27, 2015
@markstory
Copy link
Owner

Does the --config option not work?

@alvarotrigo
Copy link
Author

I haven't found any reference to that option in the wiki.

@markstory
Copy link
Owner

Its in the help for the cli tool.

I'll add it to the wiki as well.

@alvarotrigo
Copy link
Author

Right. I see it now. But yeah, it would be nice having it in the wiki as well.

@alvarotrigo
Copy link
Author

I've seen that if I have two config files and none of them has the default name asset_compress.ini, then an error appears:

Configuration file "C:\inetpub\wwwroot\cakephp\app\Config\asset_compress.ini" was not found.

Does it means I have to create an empty file with the name asset_compress.ini? Or is there a way to configure that as well?

@markstory
Copy link
Owner

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.

@alvarotrigo
Copy link
Author

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?

@markstory
Copy link
Owner

Telling the various parts of the plugin which is 'default' is the only challenging thing I think.

@markstory markstory modified the milestone: 3.0 Aug 31, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants