Linux unitednationsplay.com 3.10.0-1160.45.1.el7.x86_64 #1 SMP Wed Oct 13 17:20:51 UTC 2021 x86_64
nginx/1.20.1
Server IP : 188.130.139.92 & Your IP : 3.22.120.195
Domains :
Cant Read [ /etc/named.conf ]
User : web
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
home /
www /
unp-musonza /
vendor /
league /
flysystem /
Delete
Unzip
Name
Size
Permission
Date
Action
src
[ DIR ]
drwxr-xr-x
2020-08-23 07:39
CODE_OF_CONDUCT.md
3.28
KB
-rw-r--r--
2020-08-23 07:39
LICENSE
1.04
KB
-rw-r--r--
2020-08-23 07:39
SECURITY.md
428
B
-rw-r--r--
2020-08-23 07:39
composer.json
2.37
KB
-rw-r--r--
2020-08-23 07:39
deprecations.md
724
B
-rw-r--r--
2020-08-23 07:39
Save
Rename
# Deprecations This document lists all the planned deprecations. ## Handlers will be removed in 2.0 The `Handler` type and associated calls will be removed in version 2.0. ### Upgrade path You should create your own implementation for handling OOP usage, but it's recommended to move away from using an OOP-style wrapper entirely. The reason for this is that it's too easy for implementation details (for your application this is Flysystem) to leak into the application. The most important part for Flysystem is that it improves portability and creates a solid boundary between your application core and the infrastructure you use. The OOP-style handling breaks this principle, therefore I want to stop promoting it.