I will be building my own back-end for custom analytics. I will ensure that no private information is ever sent, only counts of which features are being used will be sent.
- Centralized logic related to fetching Valet version.
- Updating global dependencies now updates the version number of Valet
in the driver section.
- The latest version of Valet is now determined by checking Packagist.
(This only occurs when the app starts up.)
This makes it possible for PHP Monitor to request what the latest
version of Valet is. This isn't wired up to the UI currently, so
this feature isn't enabled yet.
To enable this feature, I would need to add:
- Conditional check for Valet updates (via setting)
- Decide when to run this check (either every X time and at launch)?
Additionally, PHP Monitor should be aware of its own uptime in order
to make periodic checks if the app hasn't been restarted. A check
should ideally occur every week or so if the app is not restarted.
The relevant app update check should also be adjusted to run in a very
similar way. How frequently the app checks for updates might also be
a setting but I don't want to query too often.
This should significantly speed up installs of PHP versions and also
extensions. This will become the default at some point in Homebrew's
future, but it is nice to benefit from this already.
If you serve a single folder locally multiple times, e.g. as
`cdn.mydomain.test` and `mydomain.test`, securing would fail
for domain that came alphabetically last.
This has been resolved if you are running Valet 3 or newer by
leveraging the `valet secure $domain` syntax.
