-
Couldn't load subscription status.
- Fork 2.1k
docs: update "going to production" guide #4398
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is really good! I'm going to follow up with a commit to add trusted documents to the advice, users who use trusted documents can mostly skip over disabling introspection, query cost analysis, and similar concerns.
|
Follow up with trusted documents can be found here: #4418 |
Expands on #4398 by recommending the trusted documents pattern which 90+% of GraphQL users should be using.
Updates "Going to Production" guide to cover a larger scope. The goal is to cover most bases on what devs should consider before deploying to production. I also added a checklist. --------- Co-authored-by: Benjie <[email protected]>
Expands on graphql#4398 by recommending the trusted documents pattern which 90+% of GraphQL users should be using.
Updates "Going to Production" guide to cover a larger scope. The goal is to cover most bases on what devs should consider before deploying to production. I also added a checklist. --------- Co-authored-by: Benjie <[email protected]>
Expands on #4398 by recommending the trusted documents pattern which 90+% of GraphQL users should be using.
Updates "Going to Production" guide to cover a larger scope. The goal is to cover most bases on what devs should consider before deploying to production. I also added a checklist.
I will preface that this is a bit of a long page, but useful to have
Not ready for review yet, still proofreading/cleaning up