TheCodemasterZz / architect

bootstrap/services.php

<?php

/*
|--------------------------------------------------------------------------
| Factory Default Dependency Injector
|--------------------------------------------------------------------------
|
| The FactoryDefault Dependency Injector automatically registers the 
| right services providing a full-stack framework
|
*/

if (PHP_SAPI === 'cli') {
	$di = new \Phalcon\DI\FactoryDefault\CLI();
} else {
	$di = new \Phalcon\DI\FactoryDefault();
}

/*
|--------------------------------------------------------------------------
| Application Configs
|--------------------------------------------------------------------------
|
| Get application config parametrs from config. This file is one of the 
| important file for the framework configurations
|
*/

$appConfig = new \Phalcon\Config(
    include_once _if(APPLICATION_PATH."configs", "application.php")
);

$di->set("config", $appConfig);

/*
|--------------------------------------------------------------------------
| Error Service
|--------------------------------------------------------------------------
|
| Error Service is set by checking error config parameter in related
| enviroment folder in application config folder path. 
|
*/

$di->set('error', function () {
    return include_once APPLICATION_PATH."configs/error.php";
});	

$error = $di['error'];

/*
|--------------------------------------------------------------------------
| Session Service
|--------------------------------------------------------------------------
|
| The Session provides object-oriented wrappers to access session data.
| Reasons to use this component instead of raw-sessions:
|
| - You can easily isolate session data across applications on the same domain
| - Intercept where session data is set/get in your application
| - Change the session adapter according to the application needs
|
*/

$di->set('session', function() {
    global $di;

Use of global functionality is not recommended; it makes your code harder to test, and less reusable.

    $appConfig = $di->get('config');
    $session = new $appConfig->libraries->session();
    $session->start();
    return $session;
});

//Run session handler
$session = $di['session'];

/*
|--------------------------------------------------------------------------
| Database Service
|--------------------------------------------------------------------------
|
| Phalcon encapsulates the specific details of each database engine in 
| dialects. Those provide common functions and SQL generator to the 
| adapters.
| 
| This component allows for a lower level database manipulation than 
| using traditional models.
|
*/

$dbConfig = new \Phalcon\Config(
    include_once _if(APPLICATION_PATH."configs", "database.php")
);

foreach ($dbConfig->databases as $name => $dbConfig ) {
    $di->set($name, function() use ($dbConfig, $di){
        $className = $dbConfig["type"];
        $database =  new $className($dbConfig["config"]->toArray());
        $database->connect();
        return $database;
    });
}


/*
|--------------------------------------------------------------------------
| Mail Service
|--------------------------------------------------------------------------
|
| Mailer wrapper over SwiftMailer for Phalcon.
|
*/

$mailConfig = new \Phalcon\Config(
    include_once _if(APPLICATION_PATH."configs", "mail.php")
);

$di->set('mail', function() use ($mailConfig){
    $mailer = new \Phalcon\Ext\Mailer\Manager($mailConfig->toArray());
    return $mailer;
});


/*
|--------------------------------------------------------------------------
| Cookie Service
|--------------------------------------------------------------------------
|
| PHP automatically fills the superglobal arrays $_GET and $_POST 
| depending on the type of the request. These arrays contain the values 
| present in forms submitted or the parameters sent via the URL. The 
| variables in the arrays are never sanitized and can contain illegal 
| characters or even malicious code, which can lead to SQL injection or 
| Cross Site Scripting (XSS) attacks.
|
*/

$di->set('cookies', function() {
    global $di;

Use of global functionality is not recommended; it makes your code harder to test, and less reusable.

    $appConfig = $di->get('config');
    $cookies = new \Phalcon\Http\Response\Cookies();
    $cookies->useEncryption($appConfig->cookie_encryption);
    return $cookies;
});


/*
|--------------------------------------------------------------------------
| Response Service
|--------------------------------------------------------------------------
|
| Part of the HTTP cycle is returning responses to clients. Response is 
| the Phalcon component designed to achieve this task. HTTP responses are 
| usually composed by headers and body.
|
*/

$di->set('response', function() {
    return new \Phalcon\Http\Response();
});


/*
|--------------------------------------------------------------------------
| Asset Service
|--------------------------------------------------------------------------
|
| Phalcon\Assets is a component that allows the developer to manage static 
| resources such as css stylesheets or javascript libraries in a web 
| application.
|
*/

$di->set('assets', function () {
    $assetManager = new \Phalcon\Assets\Manager();
    return $assetManager;
}, true);

/*
|--------------------------------------------------------------------------
| Url Service
|--------------------------------------------------------------------------
|
| Phalcon\Mvc\Url is the component responsible of generate urls in a 
| Phalcon application. It’s capable of produce independent urls based on 
| routes.
|
*/

if (PHP_SAPI !== 'cli') {
    $di->set('url', function () {
        global $di;

Use of global functionality is not recommended; it makes your code harder to test, and less reusable.

        $appConfig = $di->get('config');
        $url = new \Phalcon\Mvc\Url();
        if (!is_null($appConfig->base_url))
            $url->setBaseUri($appConfig->base_url);
        return $url;
    }, true);
}

/*
|--------------------------------------------------------------------------
| Crypt Service
|--------------------------------------------------------------------------
|
| Phalcon provides encryption facilities via the Phalcon\Crypt component. 
| This class offers simple object-oriented wrappers to the mcrypt php’s 
| encryption library.
|
*/

$di->set('crypt', function () {
    global $di;

Use of global functionality is not recommended; it makes your code harder to test, and less reusable.

    $appConfig = $di->get('config');
    $crypt = new \Phalcon\Crypt();
    $crypt->setCipher($appConfig->cipher);
    $crypt->setKey($appConfig->key);
    $crypt->setMode($appConfig->encryption_mode);
    return $crypt;
}, true);

/*
|--------------------------------------------------------------------------
| Security Service
|--------------------------------------------------------------------------
|
| This component aids the developer in common security tasks such as 
| password hashing and Cross-Site Request Forgery protection (CSRF).
|
*/

$di->set('security', function() {
    global $di;

Use of global functionality is not recommended; it makes your code harder to test, and less reusable.

    $appConfig = $di->get('config');
    $security = new \Phalcon\Security();
    $security->setWorkFactor($appConfig->work_factor);
    return $security;
}, true);

/*
|--------------------------------------------------------------------------
| View Service
|--------------------------------------------------------------------------
|
| Views represent the user interface of your application. Views are often 
| HTML files with embedded PHP code that perform tasks related solely to 
| the presentation of the data. Views handle the job of providing data to 
| the web browser or other tool that is used to make requests from your 
| application.
|
*/

if (PHP_SAPI !== 'cli') {
    $di->set('view', function() {
        global $di;

Use of global functionality is not recommended; it makes your code harder to test, and less reusable.

        $appConfig = $di->get('config');
        $view = new \Phalcon\Mvc\View();
        $viewEngines = $appConfig->view_engines;
        foreach ($viewEngines as $extension => $parameters) {
            $view->registerEngines(array(
                $extension => function($view, $di) use ($parameters) {
                    $viewExtension = new $parameters->type($view, $di);
                    $viewExtension->setOptions($parameters->options->toArray());
                    return $viewExtension;
                }
            ));
        }
        return $view;
    });
}

/*
|--------------------------------------------------------------------------
| Router Service
|--------------------------------------------------------------------------
|
| The router component allows defining routes that are mapped to 
| controllers or handlers that should receive the request. A router simply 
| parses a URI to determine this information. The router has two modes: 
| MVC mode and match-only mode. The first mode is ideal for working with 
| MVC applications.
|
*/  

if (PHP_SAPI !== 'cli') {

    $di->set('router', function () {
        global $di;

Use of global functionality is not recommended; it makes your code harder to test, and less reusable.

        $appConfig = $di->get('config');
        $router = new \Phalcon\Mvc\Router\Annotations(false);
        $router->setUriSource(\Phalcon\Mvc\Router::URI_SOURCE_GET_URL); 
        $router->setUriSource(\Phalcon\Mvc\Router::URI_SOURCE_SERVER_REQUEST_URI);
        $router->setDefaults(array(
            'namespace'     => $appConfig->default_namespace,
            'module'        => $appConfig->default_module,
            'controller'    => $appConfig->default_controller,
            'action'        => $appConfig->default_method
        ));
        $router->removeExtraSlashes($appConfig->extra_slashes);
        return include_once APPLICATION_PATH."configs/routing.php";
    });
}

/*
|--------------------------------------------------------------------------
| Request Service
|--------------------------------------------------------------------------
|
| Every HTTP request (usually originated by a browser) contains additional 
| information regarding the request such as header data, files, variables, 
| etc. A web based application needs to parse that information so as to 
| provide the correct response back to the requester. Phalcon\Http\Request 
| encapsulates the information of the request, allowing you to access it 
| in an object-oriented way.
|
*/

$di->set("request", function() {
    return new \Phalcon\Http\Request();
});

/*
|--------------------------------------------------------------------------
| Filter Service
|--------------------------------------------------------------------------
|
| PHP automatically fills the superglobal arrays $_GET and $_POST 
| depending on the type of the request. These arrays contain the values 
| present in forms submitted or the parameters sent via the URL. The 
| variables in the arrays are never sanitized and can contain illegal 
| characters or even malicious code, which can lead to SQL injection or 
| Cross Site Scripting (XSS) attacks.
|
*/

$di->set("filter", function() {
    return new \Phalcon\Filter();
});

/*
|--------------------------------------------------------------------------
| Validation Service
|--------------------------------------------------------------------------
|
| Phalcon\Validation is an independent validation component that validates 
| an arbitrary set of data. This component can be used to implement 
| validation rules on data objects that do not belong to a model or 
| collection.
|
*/

$di->set("validation", function() {
    return new \Phalcon\Validation();
});