Display the "real" IP when Middleman was started

[jmuheim]

== The Middleman is loading
== LiveReload is waiting for a browser to connect
== The Middleman is standing watch at http://0.0.0.0:4567
== Inspect your site configuration at http://0.0.0.0:4567/__middleman/

This doesn't offers much when needing to access the app from another device or computer.

== The Middleman is standing watch at http://192.168.1.123:4567
== Inspect your site configuration at http://192.168.1.123:4567/__middleman/

This would be much more useful.

[Arcovion]

Yea, I was wondering how to display this

• 0.0.0.0 is used to represent all of those different IPs, but can't be used as a URL in Windows
• localhost is now used instead in Middleman v4 for that reason, but then you don't know that the server is available elsewhere
• middleman-livereload does use and show this IP (though that's partly to work around a Rack::Livereload bug)

So together with middleman-livereload you currently get all three displayed:

λ bundle exec middleman
== The Middleman is loading
== LiveReload accepting connections from http://192.168.0.3:4567 (localhost)
== The Middleman is standing watch at http://0.0.0.0:4567
== Inspect your site configuration at http://0.0.0.0:4567/__middleman/

Some computers will have multiple private IPs, or none at all. middleman-livereload just shows one of them and falls back to localhost.

Not sure what the best way is. Your suggestion is essentially merging the middleman-livereload message into core, then we can maybe remove the message from middleman-livereload...

[jmuheim]

Thanks for explaining. I'm always using LiveReload, so it doesn't bother me whether it's in core or not.

I'm looking forward to Middleman 4 then! 👍