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
|
|
|
App::bind('\\LaravelRealtimeChat\\Repositories\\Team\\TeamRepository', '\\LaravelRealtimeChat\\Repositories\\Team\\DbTeamRepository'); |
14
|
|
|
ClassLoader::addDirectories(array( |
|
|
|
|
15
|
|
|
|
16
|
|
|
app_path().'/commands', |
17
|
|
|
app_path().'/controllers', |
18
|
|
|
app_path().'/models', |
19
|
|
|
app_path().'/database/seeds', |
20
|
|
|
|
21
|
|
|
|
22
|
|
|
)); |
23
|
|
|
|
24
|
|
|
/* |
25
|
|
|
|-------------------------------------------------------------------------- |
26
|
|
|
| Application Error Logger |
27
|
|
|
|-------------------------------------------------------------------------- |
28
|
|
|
| |
29
|
|
|
| Here we will configure the error logger setup for the application which |
30
|
|
|
| is built on top of the wonderful Monolog library. By default we will |
31
|
|
|
| build a basic log file setup which creates a single file for logs. |
32
|
|
|
| |
33
|
|
|
*/ |
34
|
|
|
|
35
|
|
|
Log::useFiles(storage_path().'/logs/laravel.log'); |
36
|
|
|
|
37
|
|
|
/* |
38
|
|
|
|-------------------------------------------------------------------------- |
39
|
|
|
| Application Error Handler |
40
|
|
|
|-------------------------------------------------------------------------- |
41
|
|
|
| |
42
|
|
|
| Here you may handle any errors that occur in your application, including |
43
|
|
|
| logging them or displaying custom views for specific errors. You may |
44
|
|
|
| even register several error handlers to handle different types of |
45
|
|
|
| exceptions. If nothing is returned, the default error view is |
46
|
|
|
| shown, which includes a detailed stack trace during debug. |
47
|
|
|
| |
48
|
|
|
*/ |
49
|
|
|
|
50
|
|
|
App::error(function(Exception $exception, $code) |
|
|
|
|
51
|
|
|
{ |
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 maintenance mode is in effect for the application. |
63
|
|
|
| |
64
|
|
|
*/ |
65
|
|
|
|
66
|
|
|
App::down(function() |
67
|
|
|
{ |
68
|
|
|
return Response::make("Be right back!", 503); |
69
|
|
|
}); |
70
|
|
|
|
71
|
|
|
/* |
72
|
|
|
|-------------------------------------------------------------------------- |
73
|
|
|
| Require The Filters File |
74
|
|
|
|-------------------------------------------------------------------------- |
75
|
|
|
| |
76
|
|
|
| Next we will load the filters file for the application. This gives us |
77
|
|
|
| a nice separate location to store our route and application filter |
78
|
|
|
| definitions instead of putting them all in the main routes file. |
79
|
|
|
| |
80
|
|
|
*/ |
81
|
|
|
|
82
|
|
|
require app_path().'/filters.php'; |
83
|
|
|
|
84
|
|
|
require app_path().'/listeners.php'; |
85
|
|
|
require app_path().'/general_helpers.php'; |
86
|
|
|
require app_path().'/security_helpers.php'; |
87
|
|
|
|
The issue could also be caused by a filter entry in the build configuration. If the path has been excluded in your configuration, e.g.
excluded_paths: ["lib/*"]
, you can move it to the dependency path list as follows:For further information see https://scrutinizer-ci.com/docs/tools/php/php-scrutinizer/#list-dependency-paths