-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Invalid function when calling could code but hello function is working #1183
Comments
You shoud use absolute path for your cloud code. cloud: __dirname + './cloud/main.js' instead of cloud: './cloud/main.js', |
cloud: __dirname + "/cloud/main.js" so this is now my could path in the server.js file and this is the cloud path that i have in my app.yaml CLOUD_PATH: ./cloud/main.js . But it does not want to deploy my code... |
also tried CLOUD_PATH: "./cloud/main.js" and cloud: __dirname + "/cloud/main.js" nothing |
Please someone paste the code from app.yaml and server.js that IS working... I feel desperate :S |
not sure why you're using app.yaml parse-server and then parse-server.js should look like this:
|
Ok very weird. Now i get " Error Response: [13] Timed out when starting VM's " when i use npm run deploy but now i don't get Invalid function i get bad json. I looked into it and i do have serverURL: "https://parsetestapi.appspot.com/parse/" as i am supposed to... |
Can you just follow this? https://github.com/ParsePlatform/parse-server/wiki/Parse-Server-Guide#prerequisites |
The problem was that i did not have fileKey... i do not use files but i still need this. Thanks a lot! |
Hello. I am having this issue for over 4 days now and i have no idea how to fix it :( This is my setup
in server.js :
var parseServer = new ParseServer({
databaseURI: "XXXXXXX",
cloud: './cloud/main.js',
appId: "XXXXXX",
masterKey: "XXXXXXX",
serverURL: "https://parsetestapi.appspot.com/parse/"
});
and in app.yaml
CLOUD_PATH: './cloud/main.js'
Please help me i am desperate :D
The text was updated successfully, but these errors were encountered: