-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Seperate frankenphp(caddy) from ingress for local development #5277
Comments
Core Meeting DecisionWe vote for NGINX. We want the setup to be similar to the deployment. |
BacLuc
added a commit
to BacLuc/ecamp3
that referenced
this issue
Jul 17, 2024
That we have a more similar setup in development as in prod. Issue: ecamp#5277
BacLuc
added a commit
to BacLuc/ecamp3
that referenced
this issue
Jul 17, 2024
That we have a more similar setup in development as in prod. Issue: ecamp#5277
BacLuc
added a commit
to BacLuc/ecamp3
that referenced
this issue
Jul 17, 2024
That we have a more similar setup in development as in prod. Issue: ecamp#5277
BacLuc
added a commit
to BacLuc/ecamp3
that referenced
this issue
Jul 17, 2024
That we have a more similar setup in development as in prod. Issue: ecamp#5277
BacLuc
added a commit
to BacLuc/ecamp3
that referenced
this issue
Jul 17, 2024
That we have a more similar setup in development as in prod. Issue: ecamp#5277
BacLuc
added a commit
to BacLuc/ecamp3
that referenced
this issue
Jul 17, 2024
That we have a more similar setup in development as in prod. Issue: ecamp#5277
BacLuc
added a commit
to BacLuc/ecamp3
that referenced
this issue
Jul 17, 2024
That we have a more similar setup in development as in prod. Issue: ecamp#5277
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After merging #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:
The text was updated successfully, but these errors were encountered: