Cli\Console::setArgument

public setArgument ([array $arguments], [mixed $str], [mixed $shift]) Set an specific argument

Cli\Console::handle

public handle ([array $arguments]) Handle the whole command-line tasks

Cli\Console::addModules

public addModules (array $modules) Merge modules with the existing ones application->addModules(array( 'admin' => array( 'className' => 'Multiple\Admin\Module', 'path' => '../apps/admin/Module.php' ) ));

Cli\Console

extends abstract class Phalcon\Application implements Phalcon\Di\InjectionAwareInterface, Phalcon\Events\EventsAwareInterface Source on GitHub This component allows to create CLI applications using Phalcon Methods public addModules (array $modules) Merge modules with the existing ones application->addModules(array( 'admin' => array( 'className' => 'Multiple\Admin\Module', 'path' => '../apps/admin/Module.php' ) )); public handle ([array $arguments]) H

Class Autoloader

Phalcon\Loader allows you to load project classes automatically, based on some predefined rules. Since this component is written in C, it provides the lowest overhead in reading and interpreting external PHP files. The behavior of this component is based on the PHP’s capability of autoloading classes. If a class that does not yet exist is used in any part of the code, a special handler will try to load it. Phalcon\Loader serves as the special handler for this operation. By loading classes on a

Cherokee Installation Notes

Cherokee is a high-performance web server. It is very fast, flexible and easy to configure. Configuring Cherokee for Phalcon Cherokee provides a friendly graphical interface to configure almost every setting available in the web server. Start the cherokee administrator by executing with root /path-to-cherokee/sbin/cherokee-admin Create a new virtual host by clicking on ‘vServers’, then add a new virtual server: The recently added virtual server must appear at the left bar of the screen. In

Caching in the ORM

Every application is different, we could have models whose data change frequently and others that rarely change. Accessing database systems is often one of the most common bottlenecks in terms of performance. This is due to the complex connection/communication processes that PHP must do in each request to obtain data from the database. Therefore, if we want to achieve good performance we need to add some layers of caching where the application requires it. This chapter explains the possible poi

Cache\Multiple::start

public start (string | int $keyName, [long $lifetime]) Starts every backend

Cache\Multiple::save

public save ([string $keyName], [string $content], [long $lifetime], [boolean $stopBuffer]) Stores cached content into all backends and stops the frontend

Cache\Multiple::push

public push (Phalcon\Cache\BackendInterface $backend) Adds a backend