Make host:port configurable in the extension

[sevaseva]

The feedback site[1] mentions that 'Browser extensions always use port 35729' and, I am assuming, always on localhost.

It would be nice if the extension (Chrome, Firefox, .., any one at least?) had host:port configurable, with a user interface.

I am sure there are many cases when this is useful. Let me include one such example because I can:
Sometimes with VM based development setup such as VVV for WordPress[2] it is natural to run the guard-livereload server inside the VM. Perhaps VVV[2] would add an option to automatically set up and start guard-livereload inside the VM once this issue is resolved.

[1] http://feedback.livereload.com/knowledgebase/articles/195869-how-to-change-the-port-number-livereload-listens-o
[2] https://github.com/varying-vagrant-vagrants/vvv/

[sevaseva]

Security risks? Difficult to implement because of the way it's designed?
If none of the above and someone can point me in the right direction, I might (not to over promise) offer a PR.

Thank you!

Order of importance for me: Chrome, Firefox, (other browsers are marginally interesting).

[sevaseva]

Or does the extension try to connect to current page/URL host (and port 35729)? It seems it does.
If so, additional configurability adds less value (although still does). Most VM configurations should work fine as long as port 35729 is not used by something else that hardcodes ports..