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

[ISSUE 597] Fix health check for frontend container #599

Merged
merged 5 commits into from
Oct 17, 2023

Conversation

daphnegold
Copy link
Contributor

@daphnegold daphnegold commented Oct 16, 2023

Summary

Fixes #597

Time to review: 5 mins

Changes proposed

Set hostname conditionally Terraform for frontend only, setting it in api is breaking. I think the issue is multifold... a breaking change to the way they handle hostname in next.js + AWS Fargate already having a default environment variable named HOSTNAME that overrides ours unless we explicitly set it (overriden in Dockerfile or whatever). Regardless, setting hostname to "0.0.0.0" fixes it. Tried upgrading to 13.5.5 but that didn't work.

Additional information

vercel/next.js#54133
https://github.com/vercel/next.js/pull/53131/files#diff-3a7de5f9ca3729cdc0a041e9d4c22391754e702ba49ba230daf55730bdc70d99R1975
vercel/next.js#54445
https://github.com/vercel/next.js/blob/canary/packages/next/src/build/utils.ts

Copy link
Collaborator

@acouch acouch left a comment

Choose a reason for hiding this comment

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

Fantastic! So glad to be unblocked here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Task]: Fix health check for frontend container
2 participants