The Parse Platform has changed a lot over the past few months with the departure of one core contributor and the arrival of new contributors. We also look back at the successes of the last year and what’s in the works for the coming months.
The summer has been really busy and we’ve dusted off the JS SDK, stripping out large parts of its legacy.
Backbone style callbacks are definitely out.
We’d like to take a moment to say thank you to everyone in the community and beyond.
It’s been a great year and we couldn’t be providing all that is parse without everyone’s help.
Version 1.4.0 of the Parse PHP SDK is now available for use.
This is a jump from 1.3.0 which now includes quite a few new features. Among them being relative time queries, aggregate queries and index management.
Hacktoberfest 2017 is underway!
We encourage you to take the time to sign up for Hacktoberfest and start contributing to parse-server or other open source projects on github.
You can find more details and signup here, oh and did we mention there are free t-shirts?
Version 1.3.0 of the Parse PHP SDK is now available for use.
This is a jump from 1.2.10 which now includes support for HHVM, full text query support and more!
A security issue was recently disclosed for Node.js. This affects versions of node starting at the 4.x line, all the way through 8.x.
As it stands security updates were released a week ago and are currently available for all active release lines (including 7.x). We highly recommend you update your implementations to patch this issue (assuming you haven’t already).
You’ll find this post in your
_posts directory. Go ahead and edit it and re-build the site to see your changes. You can rebuild the site in many different ways, but the most common way is to run
jekyll serve, which launches a web server and auto-regenerates your site when a file is updated.
To add new posts, simply add a file in the
_posts directory that follows the convention
YYYY-MM-DD-name-of-post.ext and includes the necessary front matter. Take a look at the source for this post to get an idea about how it works.
As we previously shared, the Parse service is shutting down at the end of this month. Specifically, we will disable the Parse service on Monday, January 30, 2017. Throughout the day we will be disabling the Parse API on an app-by-app basis. When your app is disabled, you will not be able to access the data browser or export any data, and your applications will no longer be able to access the Parse API.
The holidays are upon us! Thanksgiving has come and gone, and Christmas is coming up in just three and a half weeks. This leaves app developers little time to enjoy a stress-free app update.