parse-server

问题 I currently have a project that's being migrated away from Parse Server but needs to maintain backwards compatibility. Since Parse Server generates it's own object Ids, rather than using Mongo's I'd like to know: How does Parse Server generate it's objectIds? and why does it do this when MongoDB has great objectId generation natively? Will parse be able to work with objects with non-Parse generated IDs? An example: _id: "LvIzxv5spL" // created by Parse Server _id: "507f1f77bcf86cd799439011" /

问题 i am running my migrated app on Heroku Parse-Server. When i try to send a password reset email from my app using 'requestPasswordResetInBackground' i get the following error: "An appName, publicServerURL, and emailAdapter are required for password reset functionality.". It used to work fine on Parse.com. I’ve read about initiatives for implementing this missing functionality. Does anybody know if such an implementation is already available or will be soon, and if so how to configure it?

问题 I have a parse server deployed on heroku. I am running some cloud code on my parse server its a code that takes several minutes to run and causes timeout errors on Heroku when run on a web dyno. heroku[router]: at=error code=H12 desc="Request timeout" method=POST path="/parse/functions/timeScore My understanding is if I can make the cloud code run on a worker dyno there won't be any timeout error. Is this correct? So now I have a web and worker dyno running on my app. And here is my Procfile

问题 I have a parse-server deployed with Heroku (from my GitHub repo) and hosted by mongoLab. I am attempting to send scheduled push notifications within my app and kue seems to be the most viable option. However, as I am very unfamiliar with it, I am not sure the way to approach it. I believe I have correctly installed kue on my server (through GitHub). Now, I would like to schedule this code to be executed at a date in the future: Parse.Cloud.define("sendPush", function(request, response) { var

问题 I am using the Parse Server Simple Mailgun Adapter, and my Parse Server is working perfectly on Heroku. I am new to node.js and Express, but I installed the adapter on the root of the Parse Server via: npm i parse-server-simple-mailgun-adapter This created a node_modules folder and essentially cloned the Github repository for the Mailgun Adapter. My index.js Parse Server configuration looks like: var api = new ParseServer({ verifyUserEmails: true, databaseURI: databaseUri || 'mongodb:/

问题 I am trying to connect a new android project with the parse-server-example (locally) and showing it with the parse-dashboard. I have successfully linked parse-server-example with parse-dashboard...(by changing appId and masterKey in parse-server-example/index.js and in parse-dashboard/parse-dashboard-config.json). I have installed mongodb and everything (mongodb,parse-server-example and parse-dashboard is working perfectly). But now when i am trying to initialize parse server in android

问题 I am doing migration from my Parse hosted applications to ParseServer running on AWS or Heroku slowly. The Heroku "guide to deploy to Heroku and MongoLab" uses "Parse-server-example" on GitHub while the ParseServer wiki mentions cloning "Parse-server" instead. In particular, "Parse-server" repository does not contain the "cloud\main.js" file which is the cloud function file. If I want to run ParseServer locally or on AWS, which one of those two should I use? What are the differences between

问题 I have created the project for parse cloud code and now I am trying to start it using node.js When I run start npm command it gives following error. :\Project>npm start > parse-server-example@1.4.0 start C:\Project > node index.js 1 C:\Project\node_modules\express\lib\express.js:89 throw new Error('Most middleware (like ' + name + ') is no longer bundled with Express and must be installed separately. Please see https://github.com/sen chalabs/connect#middleware.'); ^ Error: Most middleware

问题 I have a class called Project for which I create a Parse.Role for read/write permissions. Here's how I create my Role: var roleName = "hasSound_" + ident; var projectRole = new Parse.Role(roleName, new Parse.ACL()); projectRole.getUsers().add(creator); return projectRole.save().then(function(role) { var acl = new Parse.ACL(); acl.setReadAccess(role, true); //give read access to Role acl.setWriteAccess(role, true); //give write access to Role project.setACL(acl); project.save(); }); And here's

问题 TL;DR: I can get my parse dashboard talking to my locally-hosted Parse server and mongo db instance but cannot get the parse server to talk to the mLab-hosted database. I am going through the Parse migration guide and have got mongo DB, parse-server-example and parse-dashboard running locally. When I use the following details in the parse index.js file I can successfully connect the dashboard and see the test items in the database: databaseURI: 'mongodb://localhost:27017/dev', cloud: _