Fix potential launch failure by removing .DS_Store file from Caddy directory #202
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If a
.DS_Storefile winds up being created in the Caddy directory (which would happen if any files are added or removed from that directory via Finder), theimportin the first line of the Caddyfile will pull it in; this causes Caddy's startup to fail silently with aParse error: Unknown directive ':80'error, and Valet will appear to boot, but sites will not be accessible.Any attempt to ignore that file in the
importdirective also causes Caddy to balk (unless I just didn't get my glob syntax right). The solution in this PR is to delete any.DS_Storefiles in.valet/Caddy/whenever Caddy tries to start or restart.