Change default local site TLD

[philipnewcomer]

Since Chrome is now forcing all .dev domains to use HTTPS, we should change the default TLD for local sites to something else, I propose .localhost. However, this new default TLD should be configurable in the Pilothouse config file, as there does not appear to be a consensus in the industry on what the new local host TLD should be, and some folks may still want to use .dev by default if HTTPS is not a problem for their local sites.

[AaronHolbrook]

Agreed - and it's going to take a while to switch all existing sites/etc and change our frame of mind

[philipnewcomer]

I saw in the most recent Docker update release notes that "there is an RFC banning the use of subdomains of localhost". We may want to reconsider the default local site TLD of .localhost.

[philipnewcomer]

.localhost is definitely going to be a problem. Subdomains of localhost will always be resolved directly to 127.0.0.1 by the operating system, bypassing any hosts file entries. That would be an advantage on the host, eliminating the need for hosts file entries. However, that would also make it so that PHP scripts would be unable to connect back to themselves through the Nginx container, since the site URL would always resolve to the Docker container the code is running in, and the PHP containers do not accept HTTP connections. A PHP script could never make a connection to sitename.localhost. That would, for instance, break WP cron.

[Jaace]

I have started using .test for my sites.

[AaronHolbrook]

I dislike that name myself as it is not representative of what I’m using the site for. I.e. I’m not testing something, I’m developing something - I still prefer .dev if I can help it. Whatever the case is, I think making this modifiable by the user makes sense so we can allow people to adjust this should there be any issues down the road.

…

On Jan 25, 2018, 2:31 PM -0600, Jason Boyle ***@***.***>, wrote: I have started using .test for my sites. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.