Often we get queries/requests on how someone can help with the documentation, and how they can set up the docs application on their local machine so as to see changes immediately on their screen before issuing a pull request with their changes.
This blog post outlines how to set up our docs app and how you can help with the documentation effort.
TLDR; We released new docs, messed up, fixed it, enhancing it now, new translation platform.
Hello everyone!
Last week we have released a new Phalcon version 3.2 as well as our new documentation.
With Phalcon 3.2.0 there were many new features and bugs fixed. Today we will write about most important things you need to know and show some code examples of new features.
Hello everyone and Happy Father’s day!
For our Father’s day present, we are extremely happy to announce the release of our newest Phalcon version: 3.2.0.
Our Github issues page has well over 600 issues. However those are mostly New Feature Requests (NFRs), so we started clearing up more and more bugs as well as introducing suggested NFRs. Of course all this would not be feasible without the help of our amazing community: Thank you!
We have received the following testimony from Michael Hanekom in our team email. Michael agreed to share his experience in our blog, and we are doing so without any edits:
This is a guest post from Scott Anderson at Nanobox.
Nanobox is a portable, micro platform for developing and deploying apps. When working locally, Nanobox uses Docker to spin up and configure a virtual development environment configured to your specific needs. When you’re ready to deploy to live servers, Nanobox will take that same environment and spin it up on your cloud provider of choice, where you can then manage and scale your app through the Nanobox dashboard.
In this post, we’ll walk through getting a brand new Phalcon app up and running locally, with nothing installed other than Nanobox. First create a free Nanobox account, then download and run the Nanobox installer.
