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
Changing .dev TLD references #431
Comments
Have discussed this in previous issues. It's trivial to change for your own installation and so far there are no real .dev domains, so not going to worry about it until it's actually an issue for people. |
I'm getting the following Chrome error on all my Valet served projects using "Canary" Chrome 63.0.3223.0. "Stable" Chrome 61.0.3163.100 still seems to load .dev TLD fine. I'm not sure how quick their release cycle is but it looks like the change is coming.
|
Agreed: the change is coming quickly. But you don't have to wait for the merge. Simply run (If you don't like |
Thanks @drbyte! Just found that in the command list a few minutes ago. To @adamwathan's point it's super easy to change but could become a stumbling point for new comers with the default installation. Thanks for ref to the other conversations. Looks like bases are covered between potential merges on laravel/valet and laravel/docs. |
@adamwathan false. This is not fixed. |
It is fixed, Valet uses |
There are situations where using the actual domain is imperative (multisite installs with sub-domains). There should be a way to run valet secure "ACTUAL DOMAIN" without this overhead. |
@OrbitalStudios Your comment isn't particularly clear. Could you create a new issue and try to go into more detail there? Thanks! |
Just to let you know, people are starting to use the |
Following on from the discussion in: https://github.com/laravel/docs/issues/3526
It might be worth adopting
.localhost
instead of.dev
TLD since google has registered this.The text was updated successfully, but these errors were encountered: