evtimmy comments

Repositories
Issues
Comments

Results 3 comments of


                                            evtimmy

Inconsistent config validation when starting a server instance via CLI vs. API

Just stumbled upon this trying to configure 'auth' option in config.json, server starting from CLI (default docker image). This breaks 'auth' option for CLI server. Any work-arounds?

Inconsistent config validation when starting a server instance via CLI vs. API

I see 'auth' issue is fixed in 5.5.3, here https://github.com/parse-community/parse-server/pull/8669/files thanks!

Inconsistent config validation when starting a server instance via CLI vs. API

Is the configuration options validation that is performed on starting the server via CLI also performed when starting the server via API and if so, which parse-server version fixed that?