fix(gunicorn): support GUNICORN_KEEP_ALIVE setting in Procfile and Dockerfile - #8556
siddiqueirshad wants to merge 1 commit into
Conversation
|
@siddiqueirshad is attempting to deploy a commit to the Flagsmith Team on Vercel. A member of the Team first needs to authorize it. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthroughThe Priority: ➖ Normal Estimated code review effort: 1 (Trivial) | ~5 minutes Severity of issue fixed: Medium Merge Risk: ⚪ Minimal · up to No actionable merge-blocking risk is established; the default behavior remains consistent. ✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Hi @siddiqueirshad , thanks for the contribution, but this doesn't resolve #8543. This merely resolves it when the Procfile is used (for Heroku-like deployments). You'll need to take a look at the Flagsmith/flagsmith-common repository in order to fully resolve the issue. |
|
Hi @khvn26, when you get a chance, could you please take a look at this PR? Thanks! |
Fixes #8543. Enables GUNICORN_KEEP_ALIVE environment variable in �pi/Procfile and Dockerfile to configure HTTP keep-alive timeout.