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
When setting config.vm.host_name in the Vagrantfile, there are certain characters that won't work. Add a short warning reminding the user of this potential gotcha. Perhaps it is just sub-domains that aren't allowed due to the VirtualBox, Vagrant, networking setup, et. al. components of our dev environment. In any case, here's an explanation of valid characters: http://en.wikipedia.org/wiki/Hostname#Restrictions_on_valid_host_names
For example, we'll be unable to resolve the url if we use a . in the host_name.
Bad host_name:test.example results in http://test.example.local being unresolvable.
Good host_name:test-example results in http://test-example.local being resolvable.
The text was updated successfully, but these errors were encountered:
When setting
config.vm.host_name
in the Vagrantfile, there are certain characters that won't work. Add a short warning reminding the user of this potential gotcha. Perhaps it is just sub-domains that aren't allowed due to the VirtualBox, Vagrant, networking setup, et. al. components of our dev environment. In any case, here's an explanation of valid characters: http://en.wikipedia.org/wiki/Hostname#Restrictions_on_valid_host_namesFor example, we'll be unable to resolve the url if we use a
.
in the host_name.Bad host_name:
test.example
results inhttp://test.example.local
being unresolvable.Good host_name:
test-example
results inhttp://test-example.local
being resolvable.The text was updated successfully, but these errors were encountered: