|
1
|
|
|
<?php |
|
2
|
|
|
|
|
3
|
|
|
/* |
|
4
|
|
|
|-------------------------------------------------------------------------- |
|
5
|
|
|
| Register The Laravel Class Loader |
|
6
|
|
|
|-------------------------------------------------------------------------- |
|
7
|
|
|
| |
|
8
|
|
|
| In addition to using Composer, you may use the Laravel class loader to |
|
9
|
|
|
| load your controllers and models. This is useful for keeping all of |
|
10
|
|
|
| your classes in the "global" namespace without Composer updating. |
|
11
|
|
|
| |
|
12
|
|
|
*/ |
|
13
|
|
|
|
|
14
|
|
|
ClassLoader::addDirectories([ |
|
15
|
|
|
|
|
16
|
|
|
app_path().'/commands', |
|
17
|
|
|
app_path().'/controllers', |
|
18
|
|
|
app_path().'/models', |
|
19
|
|
|
app_path().'/database/seeds', |
|
20
|
|
|
|
|
21
|
|
|
]); |
|
22
|
|
|
|
|
23
|
|
|
/* |
|
24
|
|
|
|-------------------------------------------------------------------------- |
|
25
|
|
|
| Application Error Logger |
|
26
|
|
|
|-------------------------------------------------------------------------- |
|
27
|
|
|
| |
|
28
|
|
|
| Here we will configure the error logger setup for the application which |
|
29
|
|
|
| is built on top of the wonderful Monolog library. By default we will |
|
30
|
|
|
| build a rotating log file setup which creates a new file each day. |
|
31
|
|
|
| |
|
32
|
|
|
*/ |
|
33
|
|
|
|
|
34
|
|
|
$logFile = 'log-'.php_sapi_name().'.txt'; |
|
35
|
|
|
|
|
36
|
|
|
Log::useDailyFiles(storage_path().'/logs/'.$logFile); |
|
37
|
|
|
|
|
38
|
|
|
/* |
|
39
|
|
|
|-------------------------------------------------------------------------- |
|
40
|
|
|
| Application Error Handler |
|
41
|
|
|
|-------------------------------------------------------------------------- |
|
42
|
|
|
| |
|
43
|
|
|
| Here you may handle any errors that occur in your application, including |
|
44
|
|
|
| logging them or displaying custom views for specific errors. You may |
|
45
|
|
|
| even register several error handlers to handle different types of |
|
46
|
|
|
| exceptions. If nothing is returned, the default error view is |
|
47
|
|
|
| shown, which includes a detailed stack trace during debug. |
|
48
|
|
|
| |
|
49
|
|
|
*/ |
|
50
|
|
|
|
|
51
|
|
|
App::error(function (Exception $exception, $code) { |
|
|
|
|
|
|
52
|
|
|
Log::error($exception); |
|
53
|
|
|
}); |
|
54
|
|
|
|
|
55
|
|
|
/* |
|
56
|
|
|
|-------------------------------------------------------------------------- |
|
57
|
|
|
| Maintenance Mode Handler |
|
58
|
|
|
|-------------------------------------------------------------------------- |
|
59
|
|
|
| |
|
60
|
|
|
| The "down" Artisan command gives you the ability to put an application |
|
61
|
|
|
| into maintenance mode. Here, you will define what is displayed back |
|
62
|
|
|
| to the user if maintenace mode is in effect for this application. |
|
63
|
|
|
| |
|
64
|
|
|
*/ |
|
65
|
|
|
|
|
66
|
|
|
App::down(function () { |
|
67
|
|
|
return Response::make('Be right back!', 503); |
|
68
|
|
|
}); |
|
69
|
|
|
|
|
70
|
|
|
/* |
|
71
|
|
|
|-------------------------------------------------------------------------- |
|
72
|
|
|
| Require The Filters File |
|
73
|
|
|
|-------------------------------------------------------------------------- |
|
74
|
|
|
| |
|
75
|
|
|
| Next we will load the filters file for the application. This gives us |
|
76
|
|
|
| a nice separate location to store our route and application filter |
|
77
|
|
|
| definitions instead of putting them all in the main routes file. |
|
78
|
|
|
| |
|
79
|
|
|
*/ |
|
80
|
|
|
|
|
81
|
|
|
require app_path().'/filters.php'; |
|
82
|
|
|
|
This check looks from parameters that have been defined for a function or method, but which are not used in the method body.