Adding support for FrankenPHP logging#45
Open
kkozlik wants to merge 3 commits intopear:masterfrom
Open
Conversation
This file contains hidden or 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.
Add FrankenPHP logging support via
frankenphp_log()This PR adds a new PEAR Log handler that routes log messages through FrankenPHP's native
frankenphp_log()function, allowing PHP applications running under FrankenPHP to emit log output directly into FrankenPHP's own logging pipeline.What's changed
Log_Frankenhandler class that implements the standard PEAR Log interfaceWhy
When running PHP in FrankenPHP worker mode,
error_log()and similar functions may not route output the way you'd expect. Usingfrankenphp_log()ensures that log messages are handled by FrankenPHP's Caddy-based logging system, respecting its formatting and routing configuration.References
frankenphp_log()documentation