Closed
Description
New Issue Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
- I can reproduce the issue with the latest version of Parse Server.
Issue Description
verifyServerUrl
does not respect the starting state, and can log an error when the server is starting up.
Steps to reproduce
Use new startup method, and call verifyServerUrl
.
Actual Outcome
Logs "unable to connect to xxx, cloud code may not be available"
Expected Outcome
verifyServerUrl
should consider startup environment
Environment
Server
- Parse Server version:
alpha
- Operating system:
macos
- Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc):
local
Database
- System (MongoDB or Postgres):
mongo
- Database version:
5
- Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc):
atlas
Client
- SDK (iOS, Android, JavaScript, PHP, Unity, etc):
n/a
- SDK version:
n/a