🚀 Advanced Web Server Manager
Complete File Manager & Terminal - Standalone Version
By Sid Gifari | Gifari Industries
Current path:
/
/
home
/
k0934d669o2b
/
tmp
✏️
Editing: php.ini.swp
b0VIM 8.0 N�}j��{�; k0934d669o2b sg2plzcpnl505839.prod.sin2.secureserver /opt/alt/php83/etc/php.ini utf-8 U3210 #"! U tp R ��������u S ��������Q � ��������Y R r ��������Y � ��������` ��������b } ��������Z � ��������v 9 ��������h � ��������l �����g � �����Z � �����` D �����_ � �����n q ad J � R � � � � � s > = � � � a � � � = � � � y , � � � w 8 � � l & � � � � a � � � > � � o n � � � � � � D C � � � � p @ ? � � ^ ] I 5 ! � � r q % � � A @ � � � ; much more verbose when it comes to errors. We recommend using the ; php.ini-development is very similar to its production variant, except it is ; recommending using the production ini in production and testing environments. ; compatibility with older or less security conscience applications. We ; best practices at its core. But please be aware, these settings may break ; php.ini-production contains settings which hold security, performance and ; development environments. ; in production environments and one that is recommended to be used in ; PHP comes packaged with two INI files. One that is recommended to be used ;;;;;;;;;;;;;;;;;;; ; About this file ; ;;;;;;;;;;;;;;;;;;; ; you may only use these constants *after* the line that loads the extension. ; dynamically loaded extension (either a PHP extension or a Zend extension), ; If you use constants in your value, and these constants belong to a ; foo = "None" ; sets foo to the string 'None' ; foo = None ; sets foo to an empty string ; foo = ; sets foo to an empty string ; sign, or by using the None keyword: ; An empty string can be denoted by simply not writing anything after the equal ; They can be turned off using the values 0, Off, False or No. ; Boolean flags can be turned on using the values 1, On, True or Yes. ; ! boolean NOT ; ~ bitwise NOT ; & bitwise AND ; ^ bitwise XOR ; | bitwise OR ; Expressions in the INI file are limited to bitwise operators and parentheses: ; previously set variable or directive (e.g. ${foo}) ; (e.g. E_ALL & ~E_NOTICE), a quoted string ("bar"), or a reference to a ; of the INI constants (On, Off, True, False, Yes, No and None) or an expression ; The value can be a string, a number, a PHP constant (e.g. E_ALL or M_PI), one ; directive because it is not set or is mistyped, a default value will be used. ; There is no name validation. If PHP can't find an expected ; Directives are variables used to configure PHP or PHP extensions. ; Directive names are *case sensitive* - foo=bar is different from FOO=bar. ; directive = value ; Directives are specified using the following syntax: ; http://php.net/ini.sections ; CGI/FastCGI. ; at runtime. Currently, [PATH=] and [HOST=] sections only work under ; special sections cannot be overridden by user-defined INI files or ; PHP files served from www.example.com. Directives set in these ; following the section heading [HOST=www.example.com] only apply to ; apply to PHP files in the /www/mysite directory. Directives ; Directives following the section heading [PATH=/www/mysite] only ; they might mean something in the future. ; Section headers (e.g. [Foo]) are also silently ignored, even though ; beginning with a semicolon are silently ignored (as you probably guessed). ; The syntax of the file is extremely simple. Whitespace and lines ; http://php.net/configuration.file ; See the PHP docs for more specific information. ; Windows directory (usually C:\windows) ; 6. The directory from the --with-config-file-path compile time option, or the ; (otherwise in Windows) ; 5. The web server's directory (for SAPI modules), or directory of PHP ; 4. Current working directory (except CLI) ; 3. A number of predefined registry keys on Windows (As of PHP 5.2.0) ; 2. The PHPRC environment variable. (As of PHP 5.2.0) ; 1. SAPI module specific location. ; The following is a summary of its search order: ; PHP attempts to find and load this configuration from a number of locations. ; configuring many of the aspects of PHP's behavior. ; PHP's initialization file, generally called php.ini, is responsible for ;;;;;;;;;;;;;;;;;;; ; About php.ini ; ;;;;;;;;;;;;;;;;;;; [PHP] ad � � � � � � extension=i360.so opcache.fast_shutdown = 1 ; see /etc/php.d/20-ffi.ini ad $ � R � � � � | . � � � � � � q ] \ ( � � � ` � � � t P 0 � � � � q Z Y ) � � � � � � F � � e : � � I � � q , � � � � N " � � � 3 � � I % � � N � � c $ � � � � ; E_USER_NOTICE - user-generated notice message ; E_USER_WARNING - user-generated warning message ; E_USER_ERROR - user-generated error message ; E_COMPILE_WARNING - compile-time warnings (non-fatal errors) ; E_COMPILE_ERROR - fatal compile-time errors ; initial startup ; E_CORE_WARNING - warnings (non-fatal errors) that occur during PHP's ; E_CORE_ERROR - fatal errors that occur during PHP's initial startup ; and forward compatibility of your code ; to your code which will ensure the best interoperability ; E_STRICT - run-time notices, enable to have PHP suggest changes ; empty string) ; relying on the fact it is automatically initialized to an ; intentional (e.g., using an uninitialized variable and ; from a bug in your code, but it's possible that it was ; E_NOTICE - run-time notices (these are warnings which often result ; E_PARSE - compile-time parse errors ; E_WARNING - run-time warnings (non-fatal errors) ; E_RECOVERABLE_ERROR - almost fatal run-time errors ; E_ERROR - fatal run-time errors ; E_ALL - All errors and warnings (includes E_STRICT as of PHP 5.4.0) ; Error Level Constants: ; ; development and early testing. ; means it pretty much reports everything which is exactly what you want during ; Note: The php.ini-development file has this setting as E_ALL. This ; development servers and development settings are for. ; resources complaining about best practices and coding standards. That's what ; recommend error reporting setting. Your production server shouldn't be wasting ; recommended coding standards in PHP. For performance reasons, this is the ; those related to E_NOTICE and E_STRICT, which together cover best practices and ; By default, PHP is set to take action on all errors, notices and warnings EXCEPT ; some common settings and their meanings. ; operators. The error level constants are below here for convenience as well as ; directive is through the use of the error level constants and bitwise ; it to take action for. The recommended way of setting values for this ; This directive informs PHP of which errors, warnings and notices you would like ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; Error handling and logging ; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; memory_limit = 128M ; http://php.net/memory-limit ; Maximum amount of memory a script may consume ;max_input_vars = 5000 ; How many GET/POST/COOKIE input variables may be accepted ;max_input_nesting_level = 64 ; http://php.net/max-input-nesting-level ; Maximum input variable nesting level max_input_time = 60 ; http://php.net/max-input-time ; Production Value: 60 (60 seconds) ; Development Value: 60 (60 seconds) ; Default Value: -1 (Unlimited) ; Note: This directive is hardcoded to -1 for the CLI SAPI ; long running scripts. ; idea to limit this time on productions servers in order to eliminate unexpectedly ; Maximum amount of time each script may spend parsing request data. It's a good max_execution_time = 30 ; Note: This directive is hardcoded to 0 for the CLI SAPI ; http://php.net/max-execution-time ; Maximum execution time of each script, in seconds ;;;;;;;;;;;;;;;;;;; ; Resource Limits ; ;;;;;;;;;;;;;;;;;;; expose_php = On ; http://php.net/expose-php ; on your server or not. ; threat in any way, but it makes it possible to determine whether you use PHP ; (e.g. by adding its signature to the Web server header). It is no security ; Decides whether PHP may expose the fact that it is installed on the server ;;;;;;;;;;;;;;;;; ; Miscellaneous ; ;;;;;;;;;;;;;;;;;
💾 Save Changes
❌ Cancel