Skip to content

Managing app's kernel_runtime #172

Description

@marekstodolny

Hi,

While working on a project using this bundle I've noticed a few things don't work as expected.
My problem was with symfony logger/monolog and how it integrates with other components, mainly the web profiler.
I didn't have any debug data stored in my profiler and it looked like a problem with running symfony via roadrunner.

Then i found a few instances like this in the symfony codebase:

https://github.com/symfony/http-kernel/blob/0ec1b5847cf0caed0623eb3d65edd8a4de091742/Log/DebugLoggerConfigurator.php#L25

class DebugLoggerConfigurator
{
    private ?object $processor = null;

    public function __construct(callable $processor, ?bool $enable = null)
    {
        if ($enable ?? !\in_array(\PHP_SAPI, ['cli', 'phpdbg', 'embed'], true)) {
            $this->processor = \is_object($processor) ? $processor : $processor(...);
        }
    }

I think that it would be a good idea to point out that some users would want to set their own kernel_runtime mode depending on if they're building a web app. There's a few things in symfony that work differently depending on this parameter and what PHP_SAPI returns.
I didn't find any info about it and it seems like a very sensible thing to point out for anyone that might want to use your bundle.

I've managed to override the default for roadrunner (which is cli) by adding

APP_RUNTIME_MODE=web=1&cli=1

to my .env file, and those services work now as I expect them to work.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions