parse-server

I am running a clean Heroku & MLab installation of the Parse Server ( https://github.com/ParsePlatform/parse-server-example ), which I am controlling using the Parse Server Dashboard ( https://github.com/ParsePlatform/parse-dashboard ). I can make Rest API calls & create new classes. How do I prevent new classes from being created through API calls(either by logged in users or anonymously)? It looks like there is no control of this in the Parse Server Dashboard at present. I've found the answer to my question here: http://stansidel.com/2016/03/parse-server-security-considerations-and-server

PFCloud.callFunctionInBackground("hello", withParameters: ["test":"tester"]) { (response: AnyObject?, error: NSError?) -> Void in if error == nil { let responseString = response as? String print(responseString) } else { print(error!.description) } } I am getting the error: Cannot convert value of type '(AnyObject?, NSError?) -> Void' to expected argument type 'PFIdResultBlock?' (aka 'Optional<(Optional, Optional) -> ()>') Even if I add as! PFIdResultBlock , the error will not go away. How can I go about fixing this? I definitely appreciate your help on this one!! There is no need to specify

Recently I have created my own parse server hosted on heroku using mongoLab to store my data. My problem is I am saving a video as a parse PFFile , however I can not seem to be able to stream it after saving it. Here are my exact steps. First, I save the video returned by UIImagePicker //Get the video URL let videoURL = info[UIImagePickerControllerMediaURL] as? NSURL //Create PFFile with NSData from URL let data = NSData(contentsOfURL: videoURL!) videoFile = PFFile(data: data!, contentType: "video/mp4") //Save PFFile first, then save the PFUser PFUser.currentUser()?.setObject(videoFile!,

I updated the parse server to run on AWS and I get this error when I hit the reset password but the login works. I am not sure why this part of the code is having a error and not the other login and sign up. Error Domain=Parse Code=1 "{"code":1,"message":"Internal server error."}" UserInfo={error={"code":1,"message":"Internal server error."}, NSLocalizedDescription={"code":1,"message":"Internal server error."}, code=1} This is the code I have to reset it. - (void)alertView:(UIAlertView *)alertView didDismissWithButtonIndex:(NSInteger)buttonIndex { switch (alertView.alertViewStyle) { case

In a cell I want to display the time ago from the NSDate in the Parse server. Here is the code but its not working. Nothing is changing, and the data isn't being parsed. if let createdat = (object?["createdAt"] as? String){ let pastDate = Date(timeIntervalSinceNow: TimeInterval(createdat)!) cell.TimeAgo.text = pastDate.timeAgoDisplay() } extension Date { func timeAgoDisplay() -> String { let secondsAgo = Int(Date().timeIntervalSince(self)) let minute = 60 let hour = 60 * minute let day = 24 * hour let week = 7 * day if secondsAgo < minute { return "\(secondsAgo) sec ago" } else if secondsAgo <

I am trying to enable reset password and email verification for my parse-server-example installed locally. I could see we have https://github.com/parse-server-modules/parse-mailgun . But I am not clear how to use parse-mailgun in parse-server-example, I am completely lost with it. Can somebody explain or suggest steps to enable it? Regards Atul atul kumar Create account with MailGun, and get apiKey and Domain from its website. Copy and Paste below configuration under index.js file of your parse-server-example git folder at your local system.You can get this file under parse-server-example

(To be clear, Im asking this question so as to provide the answer I found in an effort to help others that have been similarly affected by the Parse closure) Parse.com recently anounced that they are closing shop January 2017 but thankfully they have made their Parse Server software open source so we can all host our own Parse server instances. I have looked into the various options available for hosting Parse Server and have decided to host mine on Heroku I loved Parse because it was so easy to use and I have no real experience with setting up a backend. I have tried to follow several guides