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.
Hello everyone!
Back in March, we asked our community to fill in a short survey, in order to gauge why people are using Phalcon, what we should be doing better etc.
The survey was very brief and consisted of the following questions:
Continuing from our yesterday’s post, we are checking the benchmarks for micro PHP frameworks.
From feedback from the community, we intend to expand this test to be a bit more realistic, offering CRUD tests, JSON responses etc. We will work on this with the community in our repo so any help and suggestions are more than welcome!
Phalcon offers the Phalcon\Mvc\Micro application, used to create micro applications. Again we hope that this blog post will give an indication on what one can expect from a Phalcon Micro application. Note that this blog and our website both run using the Phalcon Micro application. Both sites run on an Amazon VM with 512Mb RAM and 1 vCPU.
It has been quite a while since we run our benchmarks against other networks. Actually the last time we had the benchmarks in our documentation was for Phalcon 1.3! Yes we know, we have been neglecting this.
Hopefully this post will offer some perspective on what you can expect from Phalcon and your application. It goes without saying that every application needs the best design for its needs, but using Phalcon can also push your application’s performance even further.
Hey everyone!!
As part of our restructuring and working towards a better more robust framework in terms of features as well as organization, we have removed the IDE stubs from the Phalcon DevTools repository and moved to its own repository.
Since Phalcon is a module that is loaded in memory and always available, there is no way for an IDE such as PHPStorm to interrogate the sources of the framework and offer autocomplete features for namespaces, classes, methods etc.
To work around this issue, the Phalcon team has been generating IDE stubs that can be used with such IDEs.
Good morning everyone!
We would like to update you on our funding campaign. As most know, we started a funding campaign a few months back, in an effort to raise capital which will help us offer a better, faster and more feature rich framework to our community.
The funds would be used to hire specialists in C, sponsor bug fixes and features, cover expenses for potential conferences etc.
Hey everyone.
We are releasing a hotfix today 3.1.1 that addresses some urgent issues with the framework. We strongly recommend that you upgrade your Phalcon version to the latest release 3.1.1.
As with any software, we have the you broke it scenario here. Thanks to the quick reporting from the community, we managed to fix the issues that came up, and therefore issue the hotfix today.
The release tag can be found here: 3.1.1
