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.
Here at Parse, we are big fans of open source software and the communities which form to build things together. Parse Server, released just 47 days ago, has already seen 50 contributors join the team. It’s incredibly exciting to see this project moving so quickly, with new features being added along with many improvements and fixes. We’ve been open-minded to suggestions, and have favored accepting contributions over enforcing too many rules. The Parse eco-system is yours now, and it’s very important that you feel some ownership.
In this post, I will attempt to convince you that Parse Server is worthy of your time and interest, even if you’ve never heard of Parse before. I will also make the case that Parse Server is and can be objectively better than the hosted Parse service. I hope that by the end of it, you will consider evaluating it for your next project.