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

💡 Expand “Best practices” guide #811

Open
dblythy opened this issue Jan 5, 2021 · 3 comments
Open

💡 Expand “Best practices” guide #811

dblythy opened this issue Jan 5, 2021 · 3 comments

Comments

@dblythy
Copy link
Member

dblythy commented Jan 5, 2021

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.

@mtrezza
Copy link
Member

mtrezza commented Jan 5, 2021

There have been threads on GitHub and/or Parse Forum regarding this. It could be helpful if you link them here to consolidate the discussion.

In addition, there have been troubleshooting threads that you could draw material from for such a best practice document.

For example:

@dblythy
Copy link
Member Author

dblythy commented Jan 6, 2021

Of course, I've edited the original post to include some links. If you have any suggestions for topics that could be included in the section, please feel free to post them too.

@mtrezza
Copy link
Member

mtrezza commented Mar 23, 2022

Parse Server docs do have a Best Practice page.

@dblythy dblythy changed the title 💡 “Best practices” guide 💡 Expand “Best practices” guide Mar 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants