Synchronize changes from api-platform template (aka switch to FrankenPHP) - Githubissues

ecamp / ecamp3

eCamp v3 is a web-based app for camp and course planning. The application is specialized for camps and courses of youth associations and for Y+S offers in the sport of camp sports/trekking.

https://ecamp3.ch

GNU Affero General Public License v3.0

111 stars 49 forks source link

Synchronize changes from api-platform template (aka switch to FrankenPHP) #4453

Closed usu closed 3 months ago

usu commented 8 months ago

The last PRs for synchronizing changes form the official api-platform were approx. 1 year ago: https://github.com/ecamp/ecamp3/pull/3304 https://github.com/ecamp/ecamp3/pull/3255

In the meantime, the following changes were added: https://github.com/api-platform/api-platform/compare/7642f8639ff1d95cfa48832db0221973559f8d29...main

The biggest change is the move from php-fpm to frankenphp, which came out beta last month (https://laravel-news.com/frankenphp).

Do we plan to switch to FrankenPHP as well? Or do we judge this as too early?

The biggest benefits I'd see:

PHP and Caddy in 1 container instead of 2 separate ones
Potential performance benefits by running Symfony in worker mode (similar like node; boot once and then serve all incoming requests). Of course, performance improvements would need to be tested and verified first.

Remaining:

upgrade to Postgres 16
FrankenPHP runtime mode

manuelmeister commented 6 months ago

Core Meeting Discuss

Cool idea. Local dev would probably work with one container as well.
If someone want to tackle this, we are not against it.