Defaulting to having `ssi on;` in the `http` block will allow those of us doing Nginx Server Side Includes to use Valet in local development.
A longer explanation of SSI, why we want it, and the impact is here: https://github.com/laravel/valet/issues/513
Signed-off-by: Andrew Welch <andrew@nystudio107.com>
The previous method simply returned `web` if there was a file named `craft` in the $sitePath (which means we’re running Craft 3).
The problem is that many sites, especially upgraded ones, will be serving out of `public`. This is also in line with the default Forge/ServerPilot default dirs.
So we test to see if either `/web` or `/public` exist, and return them if so. Otherwise default to the current method.
Signed-off-by: Andrew Welch <andrew@nystudio107.com>
Previously testing a concrete5 site that had tons of 404s and required file based sessions would force each request to load sequentially causing the site to load pretty slowly. This change makes it so that the driver is aware of the files directory and markes anything within as a static file.
The `substr` of `-8` was based on `.dev.crt`, but since the TLD has always been configurable, this should have always been dynamic.
Running `valet links` will not show `https` or the `TLS` columns correctly if the substring matching is of the wrong length.
Fixes#144
".test" or ".dev" is really a TLD, not a "domain" in the conventional sense.
Changing the command to `valet tld` more accurately reflects the purpose of the command (to set or get the configured TLD served by Valet)
The use of `valet domain` is currently preserved as an alias for `valet tld`, but will be removed at a later date.
Fixes#144
".dev" is really a TLD, not a "domain" in the conventional sense.
Changing the command to `valet tld` more accurately reflects the purpose of the command (to set or get the configured TLD served by Valet)
