Update Docs: Expand on how Laravel Octane uses Caddyfiles #1028
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I was having some trouble ascertaining whether the default Caddyfile
/etc/caddy/Caddyfileis used while using Laravel Octane, but I found it it's actually using a stubbed Caddyfile from the Octane repo.This is still a bit misleading, as when you go to the stubbed Caddyfile it looks like you can use the environment variables that it has templated within it. This however doesn't work because when Octane boots up a process it will only add environment variables that are defined in this file. So, I also added a warning that env vars will not be respected when using Laravel Octane.