Change default IP from "localhost" to "0.0.0.0"

[cowboy]

By specifying 0.0.0.0, the server will bind to all IPs, allowing both "localhost" to continue to work (locally) as well as allowing the server to be accessed from external devices via the machine's IP or hostname.

Will this cause any problems? We would have to bump the minor version, but this change is awesome in my testing, here.

Any downsides?

[cowboy]

If people were concerned about outside access, they could just use their OS firewall to block that... but I'm finding the benefit of just being able to connect to a dev server from another machine to be incredibly useful.

[eddiemonge]

Per the docs, if the desire is to allow all ips to work, then it should be changed to hostname: '*' https://github.com/gruntjs/grunt-contrib-connect#hostname

[eddiemonge]

I think it should stay localhost and those that know what they are doing and want to allow others to connect can change their ip to *. Keep the security for the newer people are people who arent aware and let the more advanced people change it.

[cowboy]

Think about it this way:

Default to localhost, Gruntfile uses defaults

• Someone who doesn't want or care about outside access doesn't need to do anything.
• Someone who wants outside access has to modify their Gruntfile to change this option, which is an inconveince and risks accidentally committing this change to the project.

Default to 0.0.0.0, Gruntfile uses defaults

• Someone who wants outside access doesn't need to do anything.
• Someone who doesn't want or care about outside access doesn't have to touch the Gruntfile or modify the project in any way, it just works. They can enable their OS firewall if they're concerned, however, which they've probably already done if they're aware of issues like this.

I think it's more helpful to not have to modify project files unnecessarily than to worry about whether the developer in question knows what a firewall is. Besides, how often is outside access a problem? I've never joined a public wifi without first enabling my OS firewall, so I've don't really see this as an issue.

I think the benefits of defaulting to 0.0.0.0 far outweigh the drawbacks.

[cowboy]

/cc @tkellen @shama @vladikoff @sindresorhus

[tkellen]

Agreed. Do it!

[cowboy]

FWIW, when I created this task, I misunderstood how binding to localhost worked. Had I known what I know now, I would have definitely used 0.0.0.0 instead.

[vladikoff]

Sure! Bump to 0.7.0

[cowboy]

I'm going to see if there are any other changes first before releasing a new version.

[rienheuver]

On my windows 8.1 machine, this actually breaks something for me. 0.0.0.0:35729 will not access the livereload-server. Somehow 0.0.0.0 doesn't look at my machine at all (0.0.0.0:8000 gives an address invalid too).

[vatsalpande]

I am running windows 8 and if I change it to 0.0.0.0 it starts to look for ip address 0.0.0.0 and hence starts giving error