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

Local CloudCode server URL #131

Closed
r4zzz4k opened this issue Feb 1, 2016 · 1 comment
Closed

Local CloudCode server URL #131

r4zzz4k opened this issue Feb 1, 2016 · 1 comment

Comments

@r4zzz4k
Copy link
Contributor

r4zzz4k commented Feb 1, 2016

Seems like all Parse actions done within Cloud Code are against Parse.com apps and not against local Parse Server. When I started trying out Parse Server I've set all keys to corresponding keys of my Parse.com app. Now I've got 155 error in my trigger, which should not be happening as I don't see anything within parse-server repo to throw it. So looks like it was communicating with Parse.com. When I changed all keys to random string I started getting I/O errors in Android app.

Here is the code in index.js:

// Initialize the node client SDK automatically
Parse.initialize(args.appId, args.javascriptKey || '', args.masterKey);

I wasn't able to find any way to provide server url in JS SDK. Am I missing something? Anyway, JS SDK initialized with Parse Server should probably be connected to localhost.

@gfosco
Copy link
Contributor

gfosco commented Feb 2, 2016

Follow on in #132.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants