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
Integration of parse-anywhere #6
Comments
Was this using our parse-cloud-express middleware for webhooks?... What would this look like if you added it to parse-server? |
Yes it is, it spawns a subprocess with forever and injects the proper 'environment' and adds all the submodules to the path. I'd need to update a few lines to use the parse-server flavor of the hooks if required. |
Added to parse server, instead of calling |
Any metrics on usage of parse-anywhere? I was preferring to force adoption of standard node environment & modules (and making it work) over trying to emulate hosted cloud code. |
I totally understand. About 200 install last month. Some people use it frequently to debug their express app locally. |
I think parse-anywhere is very cool, and if you'd like to make a branch or a guide on using parse-anywhere with parse-server we can link to it in the Wiki. |
Ok perfect. All the compatible dependencies are there too, most notably parse-image (based on gm). If you want to put that one in the wiki too :) |
Added to the wiki a link: https://github.com/ParsePlatform/parse-server/wiki#community-links |
Update README.md
…-in-th (pull request parse-community#6) LIS-653 added beforeGetFile hook Approved-by: Daniil Lyalko
I've written parse-anywhere a while ago in order to be able to run cloud code locally.
Recently, I've deployed it through Google App Engine managed VM's in production.
The goal of parse-anywhere was to run the exact same code as you would on parse but locally, before deploying.
All the parse provided modules were re-written, or re-wrapped in order to have 100% compatibility.
Integrating it would be a nice to have for the community and avoid any code rewrite.
The text was updated successfully, but these errors were encountered: