BrettonYe 2 anni fa
parent
commit
5e5e342837

+ 1 - 1
composer.json

@@ -8,7 +8,7 @@
   ],
   "license": "GPL-3.0-or-later",
   "require": {
-    "php": "^7.2.5|^8.0",
+    "php": "^7.2.5",
     "ext-dom": "*",
     "ext-json": "*",
     "ext-mbstring": "*",

+ 163 - 0
config/telescope.php

@@ -0,0 +1,163 @@
+<?php
+
+use Laravel\Telescope\Http\Middleware\Authorize;
+use Laravel\Telescope\Watchers;
+
+return [
+
+    /*
+    |--------------------------------------------------------------------------
+    | Telescope Domain
+    |--------------------------------------------------------------------------
+    |
+    | This is the subdomain where Telescope will be accessible from. If the
+    | setting is null, Telescope will reside under the same domain as the
+    | application. Otherwise, this value will be used as the subdomain.
+    |
+    */
+
+    'domain' => env('TELESCOPE_DOMAIN', null),
+
+    /*
+    |--------------------------------------------------------------------------
+    | Telescope Path
+    |--------------------------------------------------------------------------
+    |
+    | This is the URI path where Telescope will be accessible from. Feel free
+    | to change this path to anything you like. Note that the URI will not
+    | affect the paths of its internal API that aren't exposed to users.
+    |
+    */
+
+    'path' => env('TELESCOPE_PATH', 'telescope'),
+
+    /*
+    |--------------------------------------------------------------------------
+    | Telescope Storage Driver
+    |--------------------------------------------------------------------------
+    |
+    | This configuration options determines the storage driver that will
+    | be used to store Telescope's data. In addition, you may set any
+    | custom options as needed by the particular driver you choose.
+    |
+    */
+
+    'driver' => env('TELESCOPE_DRIVER', 'database'),
+
+    'storage' => [
+        'database' => [
+            'connection' => env('DB_CONNECTION', 'mysql'),
+            'chunk' => 1000,
+        ],
+    ],
+
+    /*
+    |--------------------------------------------------------------------------
+    | Telescope Master Switch
+    |--------------------------------------------------------------------------
+    |
+    | This option may be used to disable all Telescope watchers regardless
+    | of their individual configuration, which simply provides a single
+    | and convenient way to enable or disable Telescope data storage.
+    |
+    */
+
+    'enabled' => env('TELESCOPE_ENABLED', true),
+
+    /*
+    |--------------------------------------------------------------------------
+    | Telescope Route Middleware
+    |--------------------------------------------------------------------------
+    |
+    | These middleware will be assigned to every Telescope route, giving you
+    | the chance to add your own middleware to this list or change any of
+    | the existing middleware. Or, you can simply stick with this list.
+    |
+    */
+
+    'middleware' => [
+        'web',
+        Authorize::class,
+    ],
+
+    /*
+    |--------------------------------------------------------------------------
+    | Ignored Paths & Commands
+    |--------------------------------------------------------------------------
+    |
+    | The following array lists the URI paths and Artisan commands that will
+    | not be watched by Telescope. In addition to this list, some Laravel
+    | commands, like migrations and queue commands, are always ignored.
+    |
+    */
+
+    'ignore_paths' => [
+        'nova-api*',
+    ],
+
+    'ignore_commands' => [
+        //
+    ],
+
+    /*
+    |--------------------------------------------------------------------------
+    | Telescope Watchers
+    |--------------------------------------------------------------------------
+    |
+    | The following array lists the "watchers" that will be registered with
+    | Telescope. The watchers gather the application's profile data when
+    | a request or task is executed. Feel free to customize this list.
+    |
+    */
+
+    'watchers' => [
+        Watchers\CacheWatcher::class => env('TELESCOPE_CACHE_WATCHER', true),
+
+        Watchers\CommandWatcher::class => [
+            'enabled' => env('TELESCOPE_COMMAND_WATCHER', true),
+            'ignore' => [],
+        ],
+
+        Watchers\DumpWatcher::class => env('TELESCOPE_DUMP_WATCHER', true),
+
+        Watchers\EventWatcher::class => [
+            'enabled' => env('TELESCOPE_EVENT_WATCHER', true),
+            'ignore' => [],
+        ],
+
+        Watchers\ExceptionWatcher::class => env('TELESCOPE_EXCEPTION_WATCHER', true),
+        Watchers\JobWatcher::class => env('TELESCOPE_JOB_WATCHER', true),
+        Watchers\LogWatcher::class => env('TELESCOPE_LOG_WATCHER', true),
+        Watchers\MailWatcher::class => env('TELESCOPE_MAIL_WATCHER', true),
+
+        Watchers\ModelWatcher::class => [
+            'enabled' => env('TELESCOPE_MODEL_WATCHER', true),
+            'events' => ['eloquent.*'],
+        ],
+
+        Watchers\NotificationWatcher::class => env('TELESCOPE_NOTIFICATION_WATCHER', true),
+
+        Watchers\QueryWatcher::class => [
+            'enabled' => env('TELESCOPE_QUERY_WATCHER', true),
+            'ignore_packages' => true,
+            'slow' => 100,
+        ],
+
+        Watchers\RedisWatcher::class => env('TELESCOPE_REDIS_WATCHER', true),
+
+        Watchers\RequestWatcher::class => [
+            'enabled' => env('TELESCOPE_REQUEST_WATCHER', true),
+            'size_limit' => env('TELESCOPE_RESPONSE_SIZE_LIMIT', 64),
+        ],
+
+        Watchers\GateWatcher::class => [
+            'enabled' => env('TELESCOPE_GATE_WATCHER', true),
+            'ignore_abilities' => [],
+            'ignore_packages' => true,
+        ],
+
+        Watchers\ScheduleWatcher::class => env('TELESCOPE_SCHEDULE_WATCHER', true),
+
+        Watchers\ViewWatcher::class => env('TELESCOPE_VIEW_WATCHER', true),
+    ],
+];

+ 1 - 1
config/version.php

@@ -2,5 +2,5 @@
 
 return [
     'name' => 'ProxyPanel',
-    'number' => '2.7.f',
+    'number' => '2.8.0',
 ];

BIN
database/GeoLite2-City.mmdb


BIN
database/IP2LOCATION-LITE-DB3.IPV6.BIN


+ 0 - 42
database/update/2.5.0.sql

@@ -1,42 +0,0 @@
--- 2.4.0版本以前 或 数据库以下字段为bit的 需要运行本文件来矫正数据库
-
-alter table `goods`
-    change `is_hot` `is_hot` TINYINT(1) not null default 0 comment '是否热销:0-否、1-是',
-    change `status` `status` TINYINT(1) not null default 1 comment '状态:0-下架、1-上架';
-
-alter table `node_rule`
-    change `is_black` `is_black` TINYINT(1) not null default 1 comment '是否黑名单模式:0-不是、1-是';
-
-alter table `order`
-    change `is_expire` `is_expire` TINYINT(1) not null default 0 comment '是否已过期:0-未过期、1-已过期';
-
-alter table `payment_callback`
-    change `status` `status` TINYINT(1) not null comment '交易状态:0-失败、1-成功';
-
-alter table `products_pool`
-    change `status` `status` TINYINT(1) not null default 1 comment '状态:0-未启用、1-已启用';
-
-alter table `rule_group`
-    change `type` `type` TINYINT(1) not null default 1 comment '模式:1-阻断、0-放行';
-
-alter table `ss_config`
-    change `is_default` `is_default` TINYINT(1) not null default 0 comment '是否默认:0-不是、1-是';
-
-alter table `ss_node`
-    change `is_subscribe` `is_subscribe` TINYINT(1) not null default 1 comment '是否允许用户订阅该节点:0-否、1-是',
-    change `is_ddns` `is_ddns`           TINYINT(1) not null default 0 comment '是否使用DDNS:0-否、1-是',
-    change `is_relay` `is_relay`         TINYINT(1) not null default 0 comment '是否中转节点:0-否、1-是',
-    change `is_udp` `is_udp`             TINYINT(1) not null default 1 comment '是否启用UDP:0-不启用、1-启用',
-    change `compatible` `compatible`     TINYINT(1) not null default 0 comment '兼容SS',
-    change `single` `single`             TINYINT(1) not null default 0 comment '启用单端口功能:0-否、1-是',
-    change `status` `status`             TINYINT(1) not null default 1 comment '状态:0-维护、1-正常',
-    change `v2_tls` `v2_tls`             TINYINT(1) not null default 0 comment 'V2Ray连接TLS:0-未开启、1-开启';
-
-alter table `user`
-    change `is_admin` `is_admin` TINYINT(1) not null default 0 comment '是否管理员:0-否、1-是';
-
-alter table `user_baned_log`
-    change `status` `status` TINYINT(1) not null default 0 comment '状态:0-未处理、1-已处理';
-
-alter table `user_subscribe`
-    change `status` `status` TINYINT(1) not null default 1 comment '状态:0-禁用、1-启用';