Skip to content

"host" parameter not being read from .ember-cli JSON file #4578

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

Closed
danielzen opened this issue Feb 10, 2017 · 3 comments
Closed

"host" parameter not being read from .ember-cli JSON file #4578

danielzen opened this issue Feb 10, 2017 · 3 comments

Comments

@danielzen
Copy link

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
Linux

Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:
1.0.0-beta.26 through
1.0.0-beta.30

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.
edit .ember-cli JSON object and create "host": "x.x.x.x" property. Run ng serve. host is completely ignored. However, --host command line parameter is still recognized (i.e. ng serve --host x.x.x.x)

This feature used to work, and has stopped, but I believe other .ember-cli features are still working

The log given by the failure.

Normally this include a stack trace and some more information.

Mention any other details that might be useful.

Would gladly have another way of storing settings beside .ember-cli file, but have been using them for close to a year without problem...


Thanks! We'll be in touch soon.

@beeman
Copy link
Contributor

beeman commented Feb 10, 2017

@danielzen It looks like support for this file is removed: #4030

I'm afraid at this point I can't tell you what the alternative is, as I never worked with .ember-cli.

@danielzen
Copy link
Author

Thanks @beeman. The only alternative at the moment is to manually adding the command line flags....

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants