Skip to content
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

chore: sync changes from api-platform template #3304

Merged
merged 1 commit into from
Mar 1, 2023

Conversation

usu
Copy link
Member

@usu usu commented Feb 25, 2023

Follow-up from #3255

@usu usu added the deploy! Creates a feature branch deployment for this PR label Feb 25, 2023
@github-actions
Copy link

github-actions bot commented Feb 25, 2023

Feature branch deployment currently inactive.

If the PR is still open, you can add the deploy! label to this PR to trigger a feature branch deployment.

@@ -34,17 +34,6 @@
}

:3001 {
# Matches requests for HTML documents, for static files,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PWA is still there in the referenced api-platform/api-platform@d059b22...7642f86
Is this only used for their admin application?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, they use it for their admin application. And it seems they also use NextJS to serve other static files.

This removed code is only the definition of the @pwa expression and doesn't change any behavior of Caddy alone. In the api-platform repo, this expression is reference further below in the reverse_proxy statement. We don't make use of this expression anywhere, so there's no reason in keeping it in our file. Unless we want to use similar expressions instead of our handle and handle_path directives. Don't know enough about Caddy though to know the difference between using request matchers and handle directives.

api/docker/caddy/Caddyfile Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deploy! Creates a feature branch deployment for this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants