mirror of
https://github.com/invoiceninja/invoiceninja.git
synced 2024-11-11 21:52:35 +01:00
106 lines
3.0 KiB
PHP
Executable File
106 lines
3.0 KiB
PHP
Executable File
<?php
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Register The Laravel Class Loader
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| In addition to using Composer, you may use the Laravel class loader to
|
|
| load your controllers and models. This is useful for keeping all of
|
|
| your classes in the "global" namespace without Composer updating.
|
|
|
|
|
*/
|
|
|
|
ClassLoader::addDirectories(array(
|
|
|
|
app_path().'/commands',
|
|
app_path().'/controllers',
|
|
app_path().'/models',
|
|
app_path().'/database/seeds',
|
|
app_path().'/libraries',
|
|
app_path().'/handlers',
|
|
|
|
));
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Application Error Logger
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| Here we will configure the error logger setup for the application which
|
|
| is built on top of the wonderful Monolog library. By default we will
|
|
| build a rotating log file setup which creates a new file each day.
|
|
|
|
|
*/
|
|
|
|
Log::useFiles(storage_path().'/logs/laravel.log');
|
|
|
|
|
|
/*
|
|
use Monolog\Logger;
|
|
$monolog = Log::getMonolog();
|
|
$monolog->pushHandler(new Monolog\Handler\SyslogHandler('intranet', 'user', Logger::DEBUG, false, LOG_PID));
|
|
*/
|
|
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Application Error Handler
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| Here you may handle any errors that occur in your application, including
|
|
| logging them or displaying custom views for specific errors. You may
|
|
| even register several error handlers to handle different types of
|
|
| exceptions. If nothing is returned, the default error view is
|
|
| shown, which includes a detailed stack trace during debug.
|
|
|
|
|
*/
|
|
|
|
App::error(function(Exception $exception, $code)
|
|
{
|
|
$data = [
|
|
'context' => 'PHP',
|
|
'user_id' => Auth::check() ? Auth::user()->id : 0,
|
|
'code' => $code,
|
|
'url' => Request::url(),
|
|
'user_agent' => $_SERVER['HTTP_USER_AGENT'],
|
|
'ip' => Request::getClientIp()
|
|
];
|
|
|
|
Log::error($exception, $data);
|
|
});
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Maintenance Mode Handler
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| The "down" Artisan command gives you the ability to put an application
|
|
| into maintenance mode. Here, you will define what is displayed back
|
|
| to the user if maintenace mode is in effect for this application.
|
|
|
|
|
*/
|
|
|
|
App::down(function()
|
|
{
|
|
return Response::make("Be right back!", 503);
|
|
});
|
|
|
|
|
|
|
|
Event::subscribe('UserEventHandler');
|
|
Event::subscribe('InvoiceEventHandler');
|
|
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Require The Filters File
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| Next we will load the filters file for the application. This gives us
|
|
| a nice separate location to store our route and application filter
|
|
| definitions instead of putting them all in the main routes file.
|
|
|
|
|
*/
|
|
|
|
require app_path().'/filters.php'; |