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
But John also mentioned that, in the past, he's actually done the same with SSL, which is more work and really only works long term if it's a Valet specific feature, because otherwise, he says, the config gets wiped sometimes by Valet changes.
So.. this is an idea, not a definitive plan, to make a top level feature to map a given site (parked or linked) to a non-dev TLD (e.g. "mysite.com"), secure it with SSL, and either edit the /etc/hosts file or give instructions on how to do so.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
@imjohnbon shared this article with me, talking about how to easily map a public URL to a Valet site using your
/etc/hosts
file:https://danielbachhuber.com/tip/laravel-valet-domain/
But John also mentioned that, in the past, he's actually done the same with SSL, which is more work and really only works long term if it's a Valet specific feature, because otherwise, he says, the config gets wiped sometimes by Valet changes.
So.. this is an idea, not a definitive plan, to make a top level feature to map a given site (parked or linked) to a non-dev TLD (e.g. "mysite.com"), secure it with SSL, and either edit the
/etc/hosts
file or give instructions on how to do so.Any thoughts?
Beta Was this translation helpful? Give feedback.
All reactions