Skip to content
This repository was archived by the owner on Mar 5, 2025. It is now read-only.

Issue #509: Use default hostname that works more universally. #516

Merged
merged 1 commit into from
Oct 7, 2016
Merged

Issue #509: Use default hostname that works more universally. #516

merged 1 commit into from
Oct 7, 2016

Conversation

geerlingguy
Copy link
Contributor

It looks like *.localhost domains don't work on Windows. Under Chrome and IE, with all the default settings, I would get "CONNECTION_REFUSED".

If I switch to anything without .local in the domain, things just work. So I figure why not use the pattern local.[machine-name].com.

This has two advantages:

  1. It works (I've had issues with .local and .localhost in myriad environments—not just Windows).
  2. If you have a domain like "www.example.com", with a stage env of "stage.example.com", now your local environment would be "local.example.com". So much simpler to reason about and program around if automating anything (e.g. settings.php, build scripts, etc.) since it's just [environment].example.com.

@grasmash grasmash added the Enhancement A feature or feature request label Oct 7, 2016
@grasmash grasmash merged commit 8cb4a6f into acquia:8.x Oct 7, 2016
@geerlingguy geerlingguy deleted the default-hostname-fix branch October 7, 2016 20:26
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Enhancement A feature or feature request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants