View GitHub Repository afshlim_framework

Schedule Inspection
Subscribe

Issues (47)

config/tracy.php (1 issue)

← previous file next file →
1 
<?php
2 
return [
3 
    /* Tracy debuger*/
4 
    'tracy' => [
5 
        'path' => __APP_ROOT__ . 'storage/logs/debugger/',
6 
        'active' => 1,
7 
        'showPhpInfoPanel' => 1,
8 
        'showSlimRouterPanel' => 1,
9 
        'showSlimEnvironmentPanel' => 1,
10 
        'showSlimRequestPanel' => 1,
11 
        'showSlimResponsePanel' => 1,
12 
        'showSlimContainer' =>1 ,
13 
        'showEloquentORMPanel' => 1,
14 
        'showIdiormPanel' => 1,// > 0 mean you enable logging
15 
        // but show or not panel you decide in browser in panel selector
16 
        'showDoctrinePanel' => 'em',// here also enable logging and you must enter your Doctrine container name
17 
        // and also as above show or not panel you decide in browser in panel selector
18 
        'showProfilerPanel' => 1,
19 
        'showVendorVersionsPanel' => 1,
20 
        'showXDebugHelper' =>1,
21 
        'showIncludedFiles' => 1,
22 
        'showConsolePanel' =>1,
23 
        'configs' => [
24 
            // XDebugger IDE key
25 
            'XDebugHelperIDEKey' => 'PHPSTORM',
26 
            // Disable login (don't ask for credentials, be careful) values( 1 || 0 )
27 
            'ConsoleNoLogin' => 0,
28 
            // Multi-user credentials values( ['user1' => 'password1', 'user2' => 'password2'] )
29 
            'ConsoleAccounts' => [
30 
                'dev' => '34c6fceca75e456f25e7e99531e2425c6c1de443'// = sha1('dev')
31 
            ],
32 
            // Password hash algorithm (password must be hashed) values('md5', 'sha256' ...)
33 
            'ConsoleHashAlgorithm' => 'sha1',
34 
            // Home directory (multi-user mode supported) values ( var || array )
35 
            // '' || '/tmp' || ['user1' => '/home/user1', 'user2' => '/home/user2']
36 
            'ConsoleHomeDirectory' => __APP_ROOT__,
37 
            // terminal.js full URI
38 
            'ConsoleTerminalJs' => '/assets/js/jquery.terminal.min.js',
39 
            // terminal.css full URI
40 
            'ConsoleTerminalCss' => '/assets/css/jquery.terminal.min.css',
41 
            'ProfilerPanel' => [
42 
                // Memory usage 'primaryValue' set as Profiler::enable() or Profiler::enable(1)
43 
    //                    'primaryValue' =>                   'effective',    // or 'absolute'
44 
                'show' => [
45 
                    'memoryUsageChart' => 1, // or false
46 
                    'shortProfiles' => true, // or false
47 
                    'timeLines' => true // or false
48 
                ]
49 
            ]
50 
        ]
51 
    ]
52 
];
53 
?>
0 ignored issues
– show
Best Practice introduced by
It is not recommended to use PHP's closing tag ?> in files other than templates.

Using a closing tag in PHP files that only contain PHP code is not recommended as you might accidentally add whitespace after the closing tag which would then be output by PHP. This can cause severe problems, for example headers cannot be sent anymore.

A simple precaution is to leave off the closing tag as it is not required, and it also has no negative effects whatsoever.

Loading history...
54 

            


            
                                                        
            
                                    
            
            

                
                    55
                

                                    
                                                    
                
                
                

            


            
                                                        
            
                                    
            
            

                
                    56