-
Notifications
You must be signed in to change notification settings - Fork 129
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
Option for adding 127.0.0.1 entries #91
Comments
@crussell52 I worry about the localhost getting polluted. Is this a worry for anyone else? What about using vagrant's forwarded ports? |
One of the work-arounds I had for the VPN-scenario is to use In reality, I would still be using port forwarding in conjunction with the hosts rewriting to reach the application via: I'm wouldn't be over-concerned about localhost becoming polluted since hostsupdater does such a great job of cleaning up after itself. Only boxes that were running (and configured) would have registered localhost entries. What I don't know is what the expected behavior would be if both |
This is taken care of by default with the latest release with this PR #23 |
In some cases, it is preferable to connect to the vagrant machine using localhost and forwarded ports.
(One such case is when on a securely configured VPN which sucks up all LAN traffic.)
In these cases, it would be very convenient if there was an plugin option enabling localhost entries.
It may also make sense to add a similar flag to turn off private network IPs. That way, the following configuration would result in entries for only localhost.
This would be more convenient than adding the "skip" option to the private network, especially in cases where there are multiple IPs configured.
The text was updated successfully, but these errors were encountered: