diff --git a/.gitee/ISSUE_TEMPLATE.zh-CN.md b/.gitee/ISSUE_TEMPLATE.zh-CN.md
deleted file mode 100644
index f09d98d..0000000
--- a/.gitee/ISSUE_TEMPLATE.zh-CN.md
+++ /dev/null
@@ -1,13 +0,0 @@
-### 该问题是怎么引起的？
-
-
-
-### 重现步骤
-
-
-
-### 报错信息
-
-
-
-
diff --git a/LICENSE b/LICENSE
deleted file mode 100644
index 261eeb9..0000000
--- a/LICENSE
+++ /dev/null
@@ -1,201 +0,0 @@
- Apache License
- Version 2.0, January 2004
- http://www.apache.org/licenses/
-
- TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
- 1. Definitions.
-
- "License" shall mean the terms and conditions for use, reproduction,
- and distribution as defined by Sections 1 through 9 of this document.
-
- "Licensor" shall mean the copyright owner or entity authorized by
- the copyright owner that is granting the License.
-
- "Legal Entity" shall mean the union of the acting entity and all
- other entities that control, are controlled by, or are under common
- control with that entity. For the purposes of this definition,
- "control" means (i) the power, direct or indirect, to cause the
- direction or management of such entity, whether by contract or
- otherwise, or (ii) ownership of fifty percent (50%) or more of the
- outstanding shares, or (iii) beneficial ownership of such entity.
-
- "You" (or "Your") shall mean an individual or Legal Entity
- exercising permissions granted by this License.
-
- "Source" form shall mean the preferred form for making modifications,
- including but not limited to software source code, documentation
- source, and configuration files.
-
- "Object" form shall mean any form resulting from mechanical
- transformation or translation of a Source form, including but
- not limited to compiled object code, generated documentation,
- and conversions to other media types.
-
- "Work" shall mean the work of authorship, whether in Source or
- Object form, made available under the License, as indicated by a
- copyright notice that is included in or attached to the work
- (an example is provided in the Appendix below).
-
- "Derivative Works" shall mean any work, whether in Source or Object
- form, that is based on (or derived from) the Work and for which the
- editorial revisions, annotations, elaborations, or other modifications
- represent, as a whole, an original work of authorship. For the purposes
- of this License, Derivative Works shall not include works that remain
- separable from, or merely link (or bind by name) to the interfaces of,
- the Work and Derivative Works thereof.
-
- "Contribution" shall mean any work of authorship, including
- the original version of the Work and any modifications or additions
- to that Work or Derivative Works thereof, that is intentionally
- submitted to Licensor for inclusion in the Work by the copyright owner
- or by an individual or Legal Entity authorized to submit on behalf of
- the copyright owner. For the purposes of this definition, "submitted"
- means any form of electronic, verbal, or written communication sent
- to the Licensor or its representatives, including but not limited to
- communication on electronic mailing lists, source code control systems,
- and issue tracking systems that are managed by, or on behalf of, the
- Licensor for the purpose of discussing and improving the Work, but
- excluding communication that is conspicuously marked or otherwise
- designated in writing by the copyright owner as "Not a Contribution."
-
- "Contributor" shall mean Licensor and any individual or Legal Entity
- on behalf of whom a Contribution has been received by Licensor and
- subsequently incorporated within the Work.
-
- 2. Grant of Copyright License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- copyright license to reproduce, prepare Derivative Works of,
- publicly display, publicly perform, sublicense, and distribute the
- Work and such Derivative Works in Source or Object form.
-
- 3. Grant of Patent License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- (except as stated in this section) patent license to make, have made,
- use, offer to sell, sell, import, and otherwise transfer the Work,
- where such license applies only to those patent claims licensable
- by such Contributor that are necessarily infringed by their
- Contribution(s) alone or by combination of their Contribution(s)
- with the Work to which such Contribution(s) was submitted. If You
- institute patent litigation against any entity (including a
- cross-claim or counterclaim in a lawsuit) alleging that the Work
- or a Contribution incorporated within the Work constitutes direct
- or contributory patent infringement, then any patent licenses
- granted to You under this License for that Work shall terminate
- as of the date such litigation is filed.
-
- 4. Redistribution. You may reproduce and distribute copies of the
- Work or Derivative Works thereof in any medium, with or without
- modifications, and in Source or Object form, provided that You
- meet the following conditions:
-
- (a) You must give any other recipients of the Work or
- Derivative Works a copy of this License; and
-
- (b) You must cause any modified files to carry prominent notices
- stating that You changed the files; and
-
- (c) You must retain, in the Source form of any Derivative Works
- that You distribute, all copyright, patent, trademark, and
- attribution notices from the Source form of the Work,
- excluding those notices that do not pertain to any part of
- the Derivative Works; and
-
- (d) If the Work includes a "NOTICE" text file as part of its
- distribution, then any Derivative Works that You distribute must
- include a readable copy of the attribution notices contained
- within such NOTICE file, excluding those notices that do not
- pertain to any part of the Derivative Works, in at least one
- of the following places: within a NOTICE text file distributed
- as part of the Derivative Works; within the Source form or
- documentation, if provided along with the Derivative Works; or,
- within a display generated by the Derivative Works, if and
- wherever such third-party notices normally appear. The contents
- of the NOTICE file are for informational purposes only and
- do not modify the License. You may add Your own attribution
- notices within Derivative Works that You distribute, alongside
- or as an addendum to the NOTICE text from the Work, provided
- that such additional attribution notices cannot be construed
- as modifying the License.
-
- You may add Your own copyright statement to Your modifications and
- may provide additional or different license terms and conditions
- for use, reproduction, or distribution of Your modifications, or
- for any such Derivative Works as a whole, provided Your use,
- reproduction, and distribution of the Work otherwise complies with
- the conditions stated in this License.
-
- 5. Submission of Contributions. Unless You explicitly state otherwise,
- any Contribution intentionally submitted for inclusion in the Work
- by You to the Licensor shall be under the terms and conditions of
- this License, without any additional terms or conditions.
- Notwithstanding the above, nothing herein shall supersede or modify
- the terms of any separate license agreement you may have executed
- with Licensor regarding such Contributions.
-
- 6. Trademarks. This License does not grant permission to use the trade
- names, trademarks, service marks, or product names of the Licensor,
- except as required for reasonable and customary use in describing the
- origin of the Work and reproducing the content of the NOTICE file.
-
- 7. Disclaimer of Warranty. Unless required by applicable law or
- agreed to in writing, Licensor provides the Work (and each
- Contributor provides its Contributions) on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
- implied, including, without limitation, any warranties or conditions
- of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
- PARTICULAR PURPOSE. You are solely responsible for determining the
- appropriateness of using or redistributing the Work and assume any
- risks associated with Your exercise of permissions under this License.
-
- 8. Limitation of Liability. In no event and under no legal theory,
- whether in tort (including negligence), contract, or otherwise,
- unless required by applicable law (such as deliberate and grossly
- negligent acts) or agreed to in writing, shall any Contributor be
- liable to You for damages, including any direct, indirect, special,
- incidental, or consequential damages of any character arising as a
- result of this License or out of the use or inability to use the
- Work (including but not limited to damages for loss of goodwill,
- work stoppage, computer failure or malfunction, or any and all
- other commercial damages or losses), even if such Contributor
- has been advised of the possibility of such damages.
-
- 9. Accepting Warranty or Additional Liability. While redistributing
- the Work or Derivative Works thereof, You may choose to offer,
- and charge a fee for, acceptance of support, warranty, indemnity,
- or other liability obligations and/or rights consistent with this
- License. However, in accepting such obligations, You may act only
- on Your own behalf and on Your sole responsibility, not on behalf
- of any other Contributor, and only if You agree to indemnify,
- defend, and hold each Contributor harmless for any liability
- incurred by, or claims asserted against, such Contributor by reason
- of your accepting any such warranty or additional liability.
-
- END OF TERMS AND CONDITIONS
-
- APPENDIX: How to apply the Apache License to your work.
-
- To apply the Apache License to your work, attach the following
- boilerplate notice, with the fields enclosed by brackets "[]"
- replaced with your own identifying information. (Don't include
- the brackets!) The text should be enclosed in the appropriate
- comment syntax for the file format. We also recommend that a
- file or class name and description of purpose be included on the
- same "printed page" as the copyright notice for easier
- identification within third-party archives.
-
- Copyright [yyyy] [name of copyright owner]
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
diff --git a/README.en.md b/README.en.md
deleted file mode 100644
index c164f1a..0000000
--- a/README.en.md
+++ /dev/null
@@ -1,197 +0,0 @@
-
-
-# JPower: A rapid development platform for microservices
-
-[](https://gitee.com/gdzWork/JPower) [](https://gitee.com/gdzWork/JPower)
-[](https://gitee.com/gdzWork/JPower)
-
-### QQ Number : 860452768
-> tip: After joining the group, you can get a free code generator with the screenshot of Star
--------
-
-#### JPower is just getting started, many features are still under development, so stay tuned...
-
-## JPower summary
-`JPower`It is upgraded and optimized from a government commercial project.
-
-Adopting the front-end and back-end separation model, front-end open source projects:[jpower-ui](https://gitee.com/gdzWork/jpower-ui) (basedOn AVue、Vue、Element-UI)、[JPowerWeb](https://gitee.com/deep_letters/jpower)(basedOn Vue、Element-UI)
-
-Boot version：[JPowerBoot](https://gitee.com/gdzWork/JPowerBoot)
-
-`JPower` basedOn`SpringCloud(2020.0.1)` + `SpringBoot(2.4.2)` a rapid development platform for microservices
-It has multiple modules such as unified gateway authentication, Xss anti-cross-site attack, and distributed transaction, and supports the parallel development of multi-service systems.
-Supports parallel development of multiple services and can be used as a scaffolding for the development of back-end services. The code is concise, the comments are complete, and the structure is clear. It is very suitable for learning and use as a basic framework.
-`JPower` The blueprint of the goal is to be able to create a development framework that integrates a variety of useful tools, such as configuring various reports on the page, integrating echarts to achieve rapid page generation, data transmission in various scenarios, and so on. tool.
-At present, only the basic architecture has been developed, and various tools will be gradually developed into the framework in the future.
-
-Core technology adopts spring cloud alibaba、SpringBoot、Mybatis、Seata、Sentinel、SkyWalking main frameworks and middleware。
-I hope to work hard to create a set of solutions that integrates `basic framework` —>`distributed microservice architecture` —> `tool integration` —> `system monitoring`. `This project aims to achieve basic capabilities and does not involve specific businesses. `
-
-Using JWT for Token authentication can expand and integrate Redis and other fine-grained control schemes.
-
-The registration center and configuration center select Nacos to strengthen the linkage between the modules while reducing the weight of the project.
-
-The integration of Sentinel protects the stability of services from multiple dimensions such as flow control and fuse degradation.
-
-The code generator is implemented based on MybatisPlus-generator.
-
-## Branch introduction
-1. master The branch is the latest stable version, and each commit will be upgraded with a version number
-2. dev The branch is the author's development branch. The latest code developed by the author will be submitted in real time. Those who like early adopters can switch to dev. But there may be errors, omissions, etc. If you are not familiar with the project, please don't try it.
-3. tag Each fixed version will be tagged with a tag to facilitate subsequent switching of any version.
-
-## Technical documents
-* [JPower Development Manual](https://www.kancloud.cn/guodingzhi/jpower/)
-
-## Project demonstration address
-- Project demonstration address： http://jpower.top:81
-- Super user login（Tenant code：000000）：
-- administrator： root/123456
-- Tenant user login（Tenant code：LXD0DP）：
-- Ordinary account： admin/123456
-
-> ps: No write permission in the demo environment
-
-## Business function introduction：
-1. Tenant management: super user role manages all tenant creation
-3. Organization management: department, user data maintenance, reset user password, etc.
-4. Permission settings: data permissions, role management, bind users to roles, authorize menus and resources to roles
-6. System settings: menu function, attachment management, dictionary, administrative area, system parameters, application management, etc.
-7. Gateway management: current limiting and blocking access, registration center
-8. System monitoring: interface documentation, service monitoring, SkyWalking monitoring, etc.
-
-## Project highlights feature introduction:
-1. **Service registration & discovery and invocation：**
-
- Service registration and discovery based on Nacos, using OpenFeign to realize service intermodulation, It is possible to achieve the same coding experience as calling a local method when using HTTP requests for remote calls. Developers are completely unaware that this is a remote method, let alone an HTTP request.
-
-3. **Service authentication:**
-
- JWT is used to strengthen the authorization verification of scheduling between services to ensure the security of internal services.
-
-4. **Fuse mechanism：**
-
- Because of the distribution of services, in order to avoid the "avalanche" of calls between services, Sentinel is used as a fuse to avoid the "avalanche" between services.
-
-5. **Monitor：**
-
- Use Spring Boot Admin To monitor the running status of each independent Service; use SkyWalking to view the call chain between each service, etc.
-
-6. **Link call monitoring:**
-
- At the same time, it realized SkyWalking as the full link performance monitoring of this project, Various indicators are displayed from the overall dimension to the partial dimension, and the performance information of all call chains across applications is displayed in a centralized manner, which can facilitate the measurement of overall and partial performance, and facilitate the identification of the source of the failure, which can greatly shorten the troubleshooting time in production.
-
-7. **Data permission**
-
- The data permission function is realized by using the interceptor based on Mybatis
-
-8. **Anti-cross-site scripting attack(XSS)**
-
- - Pass the filter for all requests Form parameter Filter
-
-9. **Online API**
-
- Because some functions of native swagger-ui are not friendly enough, the domestic open source is adopted`knife4j`, And made a statuser, which is convenient for springboot users to use.
-
-10. **Distributed transaction**
-
- Integrate Ali's distributed transaction middleware: seata, with **Efficient** And for business **0 intrusion** The way，Solve the distributed transaction problems faced in the microservice scenario。
-
-11. **Automatic query of dictionary data across tables, databases, and services**
-
- Used to solve the properties of cross-table, cross-database, cross-service paging data or the properties of a single object Echo the pain of dictionary data, Support for static data attributes(Data Dictionary)Automatic injection。
-
-12. **Grayscale release**
-
- In order to solve frequent service updates and launches, version rollbacks, rapid iteration, and collaborative development within the company, this project uses a modified spring-load-balancing load balancing strategy to achieve gray release.
-
-13. **Interface monitoring**
-
- In order to ensure that the interface is unblocked at any time, the monitoring of the interface is specially developed for this, and the interface monitoring of any other services can also be realized, and some custom parameter settings can be realized.
-
-## 工程结构：
-~~~
-JPower
-├── config -- Configuration file directory
-├── jpower-core-login -- Authorized login module
-├── jpower-core-server -- Core business module
-├ ├── jpower-file -- File module
-├ ├── jpower-user -- User module
-├ ├── jpower-system -- System module
-├── jpower-feign-api -- feign api
-├ ├── jpower-file-api -- File Api
-├ ├── jpower-system-api -- System Api
-├ ├── jpower-user-api -- User Api
-├── jpower-module-common -- Toolkit module
-├ ├── common-auth -- Authorization Toolkit
-├ ├── common-dbs -- Database toolkit
-├ ├── common-deploy -- Basic Startup Kit
-├ ├── common-exception -- Anomaly Toolkit
-├ ├── common-log -- Log Toolkit
-├ ├── common-nacos -- Nacos Toolkit
-├ ├── common-redis -- Cache Toolkit
-├ ├── common-feign -- The feign toolkit also integrates sentinel
-├ ├── common-swagger -- Swagger Toolkit
-├ ├── common-tool -- Basic Configuration Toolkit
-├ ├── common-transaction -- Distributed Transaction Toolkit
-├ └── common-utils -- Tools
-├── jpower-module-gateway -- Gateway module
-├── jpower-op-server -- Operation and maintenance module
-├ ├── jpower-doc -- Swagger Page
-├ ├── jpower-log -- Log Service
-└── └── jpower-admin -- SpringBootAdmin
-~~~
-
-## Technology stack：
-* The related technologies involved are
- * Cache：Redis
- * Database： MySQL 5.7
- * Persistence framework： Mybatis-plus
- * API Gateway：Gateway
- * Service registration and discovery: Nacos
- * Service consumption：OpenFeign
- * Load balancing：spring load balancing
- * Configuration Center：Nacos
- * Service fusing：Sentinel
- * Project construction：Maven 3.3
- * Distributed transaction：seata
- * Traffic Guard of Distributed System：Sentinel
- * Monitor：spring-boot-admin
- * Link call tracking&APM Monitoring：skywalking
- * Nginx
-* Deployment aspect
- * Server：CentOS
- * Docker 18
- * Nginx
-
-## Project screenshot：
-
-| Preview | Preview |
-|---|---|
-|  |  |
-|  |  |
-|  |  |
-|  |  |
-|  |  |
-|  |  |
-|  |  |
-
-# If you feel that this project is of any help to you, please click "Star" in the upper right corner to support it and promote it to your friends and colleagues, thank you!
-
-# Please submit if you find a bug [issues](https://gitee.com/gdzWork/JPower/issues)
-
-# Participate in contribution
-1. Fork This warehouse
-2. New feat_xxx Branch
-3. Submit code
-4. New Pull Request
-
-# Thanks to the free open source license provided by JetBrains:
-[](https://www.jetbrains.com/?from=lamp-cloud)
-
-# Friendship link & special thanks
-* Microservice rapid development platform：[https://gitee.com/gdzWork/JPower](https://gitee.com/gdzWork/JPower)
-* JPowerWeb [https://gitee.com/deep_letters/jpower](https://gitee.com/deep_letters/jpower)
-* jpower-ui：[https://gitee.com/gdzWork/jpower-ui](https://gitee.com/gdzWork/jpower-ui)
-* Avue：[https://gitee.com/smallweigit/avue](https://www.avuejs.com/)
-* JWchat：[https://gitee.com/CodeGI/chat](https://gitee.com/CodeGI/chat)
diff --git a/README.md b/README.md
deleted file mode 100644
index 978bfec..0000000
--- a/README.md
+++ /dev/null
@@ -1,203 +0,0 @@
-
-
-# JPower：微服务快速开发平台
-
-[](https://gitee.com/gdzWork/JPower) [](https://gitee.com/gdzWork/JPower)
-[](https://gitee.com/gdzWork/JPower)
-
-
-### QQ群 : 
- > tip: 加群后凭Star截图可免费获取代码生成器一份
--------
-
-# 接各种前后台开发、小程序，可联系微信：953944877
-
--------
-#### JPower只是刚起步，很多功能还在开发中敬请期待......
-
-## JPower 简介
-`JPower`是由一款政府商业项目升级优化而来。
-
-采用前后端分离的模式，前端开源项目：[jpower-ui](https://gitee.com/gdzWork/jpower-ui) (基于 AVue、Vue、Element-UI)、[JPowerWeb](https://gitee.com/deep_letters/jpower)(基于 Vue、Element-UI)
-
-Boot版本：[JPowerBoot](https://gitee.com/gdzWork/JPowerBoot)
-
-`JPower` 基于`SpringCloud(2020.0.1)` + `SpringBoot(2.4.2)` 的微服务快速开发平台.
-具备网关统一鉴权、Xss防跨站攻击、分布式事务等多个模块，支持多业务系统并行开发，
-支持多服务并行开发，可以作为后端服务的开发脚手架。代码简洁，注释齐全，架构清晰，非常适合学习和作为基础框架使用。
-`JPower` 的目标蓝图是能够打造一款集成各种比较好用的工具于一体的开发框架，例如可在页面配置各种报表，集成echarts可实现快速生成页面，各种场景下的数据传输等等各类工具。
-目前只是开发了基础的架构，后续会逐渐开发各种各样的工具到框架中。
-
-核心技术采用Spring Cloud Alibaba、SpringBoot、Mybatis、Seata、Sentinel、SkyWalking等主要框架和中间件。
-希望能努力打造一套集 `基础框架` —>`分布式微服务架构` —> `工具集成` —> `系统监测` 的解决方案。`本项目旨在实现基础能力，不涉及具体业务。`
-
-采用JWT做Token认证，可拓展集成Redis等细颗粒度控制方案。
-
-注册中心、配置中心选型Nacos，为工程瘦身的同时加强各模块之间的联动。
-
-集成Sentinel从流量控制、熔断降级等多个维度保护服务的稳定性。
-
-基于MybatisPlus-generator实现了代码生成器。
-
-## 分支介绍
-1. master 分支为最新的稳定版本，每次提交都会升级一个版本号
-2. dev 分支为作者的开发分支，作者开发的最新代码会实时提交上来，喜欢尝鲜的可以切换为dev。 但可能有报错、漏提等，对项目不是很熟的朋友千万别尝试。
-3. tag 每个固定的版本都会打一个tag方便后续切换任意版本。
-
-## 技术文档
-* [JPower开发手册](https://www.kancloud.cn/guodingzhi/jpower/)
-
-## 项目演示地址
-- 项目演示地址： http://jpower.top:81
-- 超级用户登录（租户编码：000000）：
-- 超级管理员： root/123456
-- 租户用户登录（租户编码：LXD0DP）：
-- 普通账号： admin/123456
-
-> ps: 演示环境中没有写入权限
-
-## 业务功能介绍：
-1. 租户管理：超级用户角色管理所有的租户创建
-3. 组织管理：部门、用户数据维护、重置用户密码等
-4. 权限设置：数据权限、角色管理、给角色绑定用户、给角色授权菜单和资源
-6. 系统设置：菜单功能、附件管理、字典、行政地区、系统参数、应用管理等
-7. 网关管理：限流和阻止访问、注册中心
-8. 系统监控：接口文档、服务监控、SkyWalking监控、ELK日志等
-
-## 项目亮点功能介绍:
-1. **服务注册&发现与调用：**
-
- 基于Nacos来实现的服务注册与发现，使用使用OpenFeign来实现服务互调, 可以做到使用HTTP请求远程调用时能与调用本地方法一样的编码体验，开发者完全感知不到这是远程方法，更感知不到这是个HTTP请求。
-
-3. **服务鉴权:**
-
- 通过JWT的方式来加强服务之间调度的权限验证，保证内部服务的安全性。
-
-4. **熔断机制：**
-
- 因为采取了服务的分布，为了避免服务之间的调用“雪崩”，采用了Sentinel的作为熔断器，避免了服务之间的“雪崩”。
-
-5. **监控：**
-
- 利用Spring Boot Admin 来监控各个独立Service的运行状态；通过SkyWalking来查看各个服务之间的调用链、堆栈等。
-
-6. **链路调用监控：**
-
- 同时实现了SkyWalking作为本项目的全链路性能监控， 从整体维度到局部维度展示各项指标，将跨应用的所有调用链性能信息集中展现，可方便度量整体和局部性能，并且方便找到故障产生的源头，生产上可极大缩短故障排除时间。
-
-7. **数据权限**
-
- 利用基于Mybatis的拦截器实现了数据权限功能
-
-8. **防跨站脚本攻击(XSS)**
-
- - 通过过滤器对所有请求中的 表单参数 进行过滤
-
-9. **在线API**
-
- 由于原生swagger-ui某些功能支持不够友好，故采用了国内开源的`knife4j`，并制作了stater，方便springboot用户使用。
-
-10. **分布式事务**
-
- 集成了阿里的分布式事务中间件：seata，以 **高效** 并且对业务 **0侵入** 的方式，解决 微服务 场景下面临的分布式事务问题。
-
-11. **跨表、跨库、跨服务的字典数据自动查询**
-
- 用于解决跨表、跨库、跨服务分页数据的属性或单个对象的属性 回显字典数据之痛, 支持对静态数据属性(数据字典)进行自动注入。
-
-12. **灰度发布**
-
- 为了解决频繁的服务更新上线，版本回退，快速迭代，公司内部协同开发，本项目采用修改spring load balancing的负载均衡策略来实现来灰度发布。
-
-13. **接口监控**
-
- 为了接口能随时保证畅通，专对于此开发了接口的监控，还可实现对其他任何服务的接口监控，可实现自定义的一些参数设置等。
-
-## 工程结构：
-~~~
-JPower
-├── config -- 配置文件目录
-├── jpower-core-login -- 授权登录模块
-├── jpower-core-server -- 核心业务模块
-├ ├── jpower-file -- 文件模块
-├ ├── jpower-user -- 用户模块
-├ ├── jpower-system -- 系统模块
-├── jpower-feign-api -- feign api模块
-├ ├── jpower-file-api -- 文件API模块
-├ ├── jpower-system-api -- 系统管理API模块
-├ ├── jpower-user-api -- 用户API模块
-├── jpower-module-common -- 工具包模块
-├ ├── common-auth -- 授权工具包
-├ ├── common-dbs -- 数据库工具包
-├ ├── common-deploy -- 基础启动工具包
-├ ├── common-exception -- 异常工具包
-├ ├── common-log -- 日志工具包
-├ ├── common-nacos -- nacos工具包
-├ ├── common-redis -- 缓存工具包
-├ ├── common-feign -- feign工具包同时集成sentinel
-├ ├── common-swagger -- swagger工具包
-├ ├── common-tool -- 基础配置工具包
-├ ├── common-transaction -- 分布式事务工具包
-├ └── common-utils -- 工具类
-├── jpower-module-gateway -- 网关模块
-├── jpower-op-server -- 运维模块
-├ ├── jpower-doc -- swagger聚合文档
-├ ├── jpower-log -- 日志服务
-└── └── jpower-admin -- SpringBootAdmin
-~~~
-
-## 技术栈：
-* 所涉及的相关的技术有
- * 缓存：Redis
- * 数据库： MySQL 5.7
- * 持久层框架： Mybatis-plus
- * API网关：Gateway
- * 服务注册与发现: Nacos
- * 服务消费：OpenFeign
- * 负载均衡：spring load balancing
- * 配置中心：Nacos
- * 服务熔断：Sentinel
- * 项目构建：Maven 3.3
- * 分布式事务：seata
- * 分布式系统的流量防卫兵：Sentinel
- * 监控：spring-boot-admin
- * 链路调用跟踪&APM监控：skywalking
- * Nginx
-* 部署方面
- * 服务器：CentOS
- * Docker 18
- * Nginx
-
-## 项目截图：
-
-| 预览 | 预览 |
-|---|---|
-|  |  |
-|  |  |
-|  |  |
-|  |  |
-|  |  |
-|  |  |
-|  |  |
-
-# 如果觉得本项目对您有任何一点帮助，请点右上角 "Star" 支持一下， 并向您的基友、同事们宣传一下吧，谢谢！
-
-# 发现bug请提交 [issues](https://gitee.com/gdzWork/JPower/issues)
-
-# 参与贡献
-1. Fork 本仓库
-2. 新建 feat_xxx 分支
-3. 提交代码
-4. 新建 Pull Request
-
-# 感谢 JetBrains 提供的免费开源 License：
-
-[](https://www.jetbrains.com/?from=lamp-cloud)
-
-# 友情链接 & 特别鸣谢
-* 微服务快速开发平台：[https://gitee.com/gdzWork/JPower](https://gitee.com/gdzWork/JPower)
-* JPowerWeb [https://gitee.com/deep_letters/jpower](https://gitee.com/deep_letters/jpower)
-* jpower-ui：[https://gitee.com/gdzWork/jpower-ui](https://gitee.com/gdzWork/jpower-ui)
-* Avue：[https://gitee.com/smallweigit/avue](https://www.avuejs.com/)
-* JWchat：[https://gitee.com/CodeGI/chat](https://gitee.com/CodeGI/chat)
-* SpringBlade [https://gitee.com/CodeGI/chat](https://gitee.com/smallc/SpringBlade)