.ember-cli settings file live-reload option not working

[zigomir]

This is my .ember-cli file

{
  "port": 4200,
  "host": "0.0.0.0",
  "live-reload": false,
  "proxy": "http://localhost:3000",
  "environment": "development"
}

I'm running ember-cli with ember server command.

But it will automatically live reload my tab in browser even though I set it to false.

[stefanpenner]

cc @twokul

[twokul]

will take a look at it

[alvincrespo]

I can confirm that these are not working for me either. I tried changing port, host, live-reload and environment and they don't seem to stick.

[rwjblue]

@twokul - Updates?

[Globegitter]

Also just tried changing proxy, output-path, etc and only proxy seems to working for me. Also was the that e.g. output-path would work for the ember build command?

[vkurchatkin]

at least port is not working with .ember-cli (--port works)

[drewcovi]

+1 port not working here either...

[rwjblue]

Yep, this is definitely a known issue. PR's fixing are welcome.

[stefanpenner]

@twokul your leaving us hanging here bro

[twokul]

will put on my list of things this week. sorry @stefanpenner

[abuiles]

@twokul quick update, this works with single word configs e.g. proxy.

The issue is that every config with more that one word (live-reload) is being passed in kebab-case to the command, they should get there in camelCase.

[twokul]

@abuiles thanks for the update. I will look into it this week.

[narayand4]

This is my .ember-cli file.
{
"port": 9999,
"host": "0.0.0.0",
"live-reload": false,
"proxy": "http://aqueous-bayou-5108.herokuapp.com/",
"environment": "development"
}
but heroku logs showing.
"Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch.
Process exited with status 137". please guide me what i'm doing wrong.
thanks.

[rwjblue]

@narayand4 - You should never deploy in such a way that runs ember-cli's server in a production environment!! Always build static assets (via ember build), and deploy those.

[twokul]

@narayand4 I believe the key should be liveReload.

[narayand4]

thaks @twokul and @rwjblue. really very knowledegable comments. i have changed liveReload keyword but still same error my app is not on production environment. i'm beginer in ember-cli when i am running my heroku logs, every time heroku logs throw this error "Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch.
Process exited with status 137".

[rwjblue]

@narayand4 - Sorry for the misleading comment earlier. What I am saying is that you should not be deploying ember-cli itself to Heroku at all. The currently recommended Heroku deployment (see here) advises using a buildpack that simply serves static files (via nginx). You can also take a look at ember-cli-divshot which simply builds and deploys locally. I plan to update the websites deployment section soon with a nice howto on using that addon.

[narayand4]

@rwjblue - thanks really you guys are awesome, ok i will see both links.

[narayand4]

thanks guys my app is running now.

i have just changed my build pack url "heroku config:set BUILDPACK_URL=https://github.com/tonycoco/heroku-buildpack-ember-cli.git" and everything working perfect.

really it's great.

[zigomir]

I believe we can close this issue since liveReload setting is now working.

For anyone, not reading all issues, just use liveReload instead of live-reload.

[pgasiorowski]

While hosting ember-cli over local network (192.168.42.160) I'm getting:
GET http://localhost:35729/livereload.js?snipver=1 net::ERR_CONNECTION_REFUSED
how do I point live-reload to the right direction (or should it detect it by default)?

[ccarterc]

Is there a solution to have live-reload not point to localhost so that I can access my site from host machine. My ember app is being served from vm and I would like to be able to access it in host or make it available on my local network so other people in office can access it.