[12.x] Add support for APP_LOCAL_SITES_PATH and APP_REMOTE_SITES_PATH to map to editor file paths #56264
+152
−0
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.
Fixes #56185
Summary
This PR introduces support for two environment variables:
APP_LOCAL_SITES_PATH
APP_REMOTE_SITES_PATH
These allow mapping container paths to host paths in editor links shown on Laravel’s exception pages, similar to the
IGNITION_LOCAL_SITES_PATH
andIGNITION_REMOTE_SITES_PATH
previously available via Ignition.Use Case
When Laravel is running inside a Docker container, file paths shown in error pages point to the container’s file system (
/var/www/html/...
), which does not exist on the host machine. This makes editor links likevscode://file/...
fail to open.With this feature, developers can map paths: