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

webhook migration instruction #52

Closed
loftyet opened this Issue Jan 29, 2016 · 3 comments

Comments

Projects
None yet
4 participants
@loftyet

loftyet commented Jan 29, 2016

Do we have any webhook migration instruction?
based on this example app: https://github.com/ParsePlatform/CloudCode-Express
should I just change the 'https://api.parse.com/1/hooks/triggers' to my heroku app url + /hooks/triggers?

Thanks,

@gfosco

This comment has been minimized.

Show comment
Hide comment
@gfosco

gfosco Jan 29, 2016

Collaborator

Webhooks isn't supported coming from api.parse.com, but cloud code is supported for writing triggers/functions directly through parse-server. What was the context in which you wanted to run parse-server and also webhooks?

Collaborator

gfosco commented Jan 29, 2016

Webhooks isn't supported coming from api.parse.com, but cloud code is supported for writing triggers/functions directly through parse-server. What was the context in which you wanted to run parse-server and also webhooks?

@gfosco gfosco closed this Jan 30, 2016

@ITpakar

This comment has been minimized.

Show comment
Hide comment
@ITpakar

ITpakar Sep 6, 2016

@gfosco I have the same issue. I added triggers and functions directly on parse-server but how do I expose and connect it to the events(like beforesave, aftersave)

ITpakar commented Sep 6, 2016

@gfosco I have the same issue. I added triggers and functions directly on parse-server but how do I expose and connect it to the events(like beforesave, aftersave)

@DeDuckProject

This comment has been minimized.

Show comment
Hide comment
@DeDuckProject

DeDuckProject Dec 16, 2016

Here's a workaround:
#234

DeDuckProject commented Dec 16, 2016

Here's a workaround:
#234

BernhardHarrer pushed a commit to BernhardHarrer/parse-server that referenced this issue Feb 22, 2017

Merge pull request parse-community#52 from JustinBeckwith/master
add instructions for deploying to Google App Engine
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment