ref(python): Add a warning about uWSGI to all WSGI frameworks #9166
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
|
Hi Ivana! To reuse the same warning on multiple pages, you can add a new include file in sentry-docs/includes (example). Then you can reference it in your docs like this file does. Hope that helps! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pre-merge checklist
If you work at Sentry, you're able to merge your own PR without review, but please don't unless there's a good reason.
Description of changes
We've had bug reports from folks in the Python SDK that were due to incorrect uWSGI server setup. Since the impact of such misconfiguration can be severe (uWSGI workers crashing), we should call this out in the docs of all integrations that can be used with uWSGI.
See getsentry/sentry-python#2738
Note to the docs team: If there's a way to reuse the same warning on multiple pages, please let me know!