Add configuration store on server

[mtrezza]

New Feature / Enhancement Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.

Current Limitation

Parse Dashboard has options that are:

• stored locally in browser, which makes them not persistent
• set via dashboard config file, which makes them difficult to maintain because they require code changes and re-deployment

Feature / Enhancement Description

Store options server side.

This can be easily achieved by specifying the class name to which options are written and from where options are read. It requires no changes in Parse Server code. It is also in line with the concept that Parse Dashboard deserves no special treatment (dedicated internal hidden classes, etc.) and is considered just another client from the viewpoint of Parse Server.

Parse Server should become the only place where options are stored, and the use of browser storage and config via file should be replaced by it whenever an option is moved to the server store. This solution opens up many possibilities in the future, for example user based settings in combination with _User based login #2311.

Example Use Case

• Store remote config history server side #2339

[parse-github-assistant]

Thanks for opening this issue!

• 🎉 We are excited about your ideas for improvement!