Closed usu closed 1 week ago
After merging https://github.com/ecamp/ecamp3/pull/5123, I'd propose that we separate the path-forwarding functionality (ingress) from frankenphp.
Combining this has a few disadvantages:
The 2nd point comes from the fact that the processing order is different between dev and prod:
Adding a separate ingress on local dev would make the two more similar and hence less error prone.
As ingress we could use:
We vote for NGINX. We want the setup to be similar to the deployment.
After merging https://github.com/ecamp/ecamp3/pull/5123, I'd propose that we separate the path-forwarding functionality (ingress) from frankenphp.
Combining this has a few disadvantages:
The 2nd point comes from the fact that the processing order is different between dev and prod:
Adding a separate ingress on local dev would make the two more similar and hence less error prone.
As ingress we could use: