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
The change of the default domain suffix from ".lndo.site" to ".lando" would bring multiple quality of life improvements to developers.
For backwards compatibility, you could just add ".lando" to the default list of supported domain suffixes.
Having a multipart domain suffix causes issues with .htaccess and local DNS rules for sites with advanced configuration.
Special rules need to be written in .htaccess and local domain forwarders.
Because the suffix is two parts instead of one, it means separate rules need to be written when creating multi-site locals for Drupal and WordPress.
Selecting the domain by regular expression should be able to match any site. Including subdomain and subside locals while also being able to target the lando local.
example:
sub-site.foo.example.com/path
sub-site.example.org/path
example.gov/sub-site
foo.example.biz/sub-site
&
sub-site.foo.example.lndo.site/path
sub-site.example.lndo.site/path
example.lndo.site/sub-site
foo.example.lndo.site/sub-site
The same regular expression should be able to match all of these domains, but cannot due to the multipart suffix.
2nd) ".lndo.site" is "lando" spelled incorrectly. I'm sure there are other reasons, but removing 1 letter to shorten the text doesn't seem like a good enough reason to cause confusion among developers trying to pick up lando.
The text was updated successfully, but these errors were encountered:
.lndo.site is an actual domain that redirects to your localhost. .lando doesn't exist as a top level domain, so the same process wouldn't be possible... IE mysite.lando isn't a domain you can buy.
.lndo.site was acquired because all the lando.* (ex: lando.com) domains were already taken...even purchasing lando.site would cost thousands of dollars.
The change of the default domain suffix from ".lndo.site" to ".lando" would bring multiple quality of life improvements to developers.
For backwards compatibility, you could just add ".lando" to the default list of supported domain suffixes.
Having a multipart domain suffix causes issues with .htaccess and local DNS rules for sites with advanced configuration.
Special rules need to be written in .htaccess and local domain forwarders.
Because the suffix is two parts instead of one, it means separate rules need to be written when creating multi-site locals for Drupal and WordPress.
Selecting the domain by regular expression should be able to match any site. Including subdomain and subside locals while also being able to target the lando local.
example:
sub-site.foo.example.com/path
sub-site.example.org/path
example.gov/sub-site
foo.example.biz/sub-site
&
sub-site.foo.example.lndo.site/path
sub-site.example.lndo.site/path
example.lndo.site/sub-site
foo.example.lndo.site/sub-site
The same regular expression should be able to match all of these domains, but cannot due to the multipart suffix.
2nd) ".lndo.site" is "lando" spelled incorrectly. I'm sure there are other reasons, but removing 1 letter to shorten the text doesn't seem like a good enough reason to cause confusion among developers trying to pick up lando.
The text was updated successfully, but these errors were encountered: