parse-community / parse-community/docs
š” Expand āBest practicesā guide
Nobody has claimed this yet.
- Dominant language
- SCSS
- Stars
- 317
- Forks
- 507
- PR merge metrics
- No merged PRs in 30d
Description
There are a number of issues that have been raised regarding firewall or other stack related issues that cannot be solved by the Parse Server package.
I think to help our community, I propose a ābest practices / recommended configuration (or even FAQ)ā section. From the top of my head, Iād imagine:
-Rate Limiting - Parse wide / specific endpoints e.g /requestPasswordReset
-Improving Performance
-Unit testing cloud code
It would be good to try to get some shared knowledge going from how the core teamās configure their own servers, especially as Iād imagine most of our developers arenāt overly experienced with application stacks.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up ā it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the linked discussions on rate limiting, performance, and unit testing Cloud Code to identify the guidance that belongs in this documentation. Done means a best-practices, recommended-configuration, or FAQ section is defined and covers the selected topics with shared operational knowledge.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100