You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
config.hostsupdater.localhost_entries=true
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.
One of the work-arounds I had for the VPN-scenario is to use localhost:8000 in my browser for reaching the application. However, I am working on a multi-tenant site where the subdomain is meaningful (part of the resolving usernames). This makes the ability to use subdomains paramount.
In reality, I would still be using port forwarding in conjunction with the hosts rewriting to reach the application via: someclient.mydomain.local:8000 where someclient.mydomain.local was mapped to localhost.
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 private_network_entries was turned on andlocalhosts_entries was turned on. I guess it would be similar to cases where two private_network IPs are present?
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: