Code changes after deploy not picked up when using Laravel Octane with FrankenPHP and Supervisor

[rico]

I would like a setup where my Laravel app is running using Octane (with FrankenPHP). To keep Octane alive I use supervisor. But I cannot find a way for Octane to pick up code changes.

artisan:octane:reload does not work in such a setup. I guess because Supervisor is not resolving the current symlink properly, or maybe something totally different which I am missing :-)

My command in the Supervisor config looks as follows: /usr/bin/php -d variables_order=EGPCS /home/user/app/current/artisan octane:start --server=frankenphp

Does anybody have an idea on how to reload the FrankenPHP workers after deploy? I also tried the approach of using the admin API of FrankenPHP directly.

[antonmedv]

What about writing a custom task and running your command from it?

task('reload', function () {
    run('/usr/bin/php -d variables_order=EGPCS /home/user/app/current/artisan octane:start --server=frankenphp');
});

[rico]

Thanks for your reply - but how does this keep octane alive? In my understanding I need something like Supervisor or Systemd to keep it alive.

[antonmedv]

Or docker.

[antonmedv]

Maybe deployer need a simple way to demonize processes.

[rico]

Or docker.

I think I would rather give up pn Octane then using Docker :-) Not my thing.

Maybe deployer need a simple way to demonize processes.

Can you elaborate?

The problem, I guess, is this:

curl http://127.0.0.1:2019/config/apps/frankenphp
{"workers":[{"file_name":"/home/user/app/releases/13/public/frankenphp-worker.php","num":2}]}

Current release is 15. Last time I did a supervisor restart app:* was at release 13.

A task that creates /home/user/app/releases/15/public/frankenphp-worker.php and reloads the config should make it work.