-
-
-
-
-
- ```
-
-#### **3. 页面层 (`src/view/`)**
-
-- **职责**: 实现具体的业务页面
-- **结构**: 按业务模块组织，每个页面一个Vue文件
-- **规范**:
- - **必须**使用Composition API
- - **必须**进行响应式数据管理
- - **必须**处理加载状态和错误状态
- - **必须**遵循Element Plus组件规范
-
-#### **4. 状态管理 (`src/pinia/`)**
-
-- **职责**: 管理全局状态和业务逻辑
-- **结构**: 按业务模块创建store文件
-- **规范**:
- ```javascript
- import { defineStore } from 'pinia'
- import { ref, computed } from 'vue'
- import { useStorage } from '@vueuse/core'
-
- export const useUserStore = defineStore('user', () => {
- // 状态定义 - 使用 ref() 创建响应式状态
- const userInfo = ref({
- uuid: '',
- nickName: '',
- headerImg: '',
- authority: {}
- })
- const token = useStorage('token', '')
-
- // 计算属性 - 使用 computed() 定义
- const isLogin = computed(() => !!token.value)
-
- // 方法定义 - 直接定义函数作为 actions
- const setUserInfo = (val) => {
- userInfo.value = val
- }
-
- const setToken = (val) => {
- token.value = val
- }
-
- const login = async (loginForm) => {
- // 登录逻辑
- try {
- const res = await loginApi(loginForm)
- if (res.code === 0) {
- setUserInfo(res.data.user)
- setToken(res.data.token)
- return true
- }
- return false
- } catch (error) {
- console.error('Login error:', error)
- return false
- }
- }
-
- const logout = async () => {
- // 登出逻辑
- token.value = ''
- userInfo.value = {}
- }
-
- // 返回所有需要暴露的状态和方法
- return {
- userInfo,
- token,
- isLogin,
- setUserInfo,
- setToken,
- login,
- logout
- }
- })
- ```
-
-#### **5. 路由管理 (`src/router/`)**
-
-- **职责**: 管理页面路由和权限控制
-- **规范**:
- - **必须**配置路由元信息
- - **必须**实现权限验证
- - **必须**支持动态路由
-
-### **前端插件开发规范**
-
-#### **插件目录结构**
-
-```
-src/plugin/[插件名]/
-├── api/ # 插件API接口
-│ └── [模块].js
-├── components/ # 插件组件（可选）
-│ └── [组件名].vue
-├── view/ # 插件页面
-│ └── [页面名].vue
-├── form/ # 插件表单（可选）
-│ └── [表单名].vue
-└── index.js # 插件入口文件（可选）
-```
-
-#### **插件开发原则**
-
-1. **独立性**: 插件应该是自包含的，不依赖其他业务模块
-2. **可配置性**: 插件应该支持配置化，便于定制
-3. **可扩展性**: 插件应该预留扩展接口
-4. **一致性**: 插件UI风格应与主系统保持一致
-
-### **代码质量要求**
-
-1. **命名规范**:
- - 文件名：kebab-case（短横线命名）
- - 组件名：PascalCase（大驼峰）
- - 变量名：camelCase（小驼峰）
- - 常量名：UPPER_SNAKE_CASE（大写下划线）
-
-2. **注释规范**:
- - **必须**为所有API函数添加JSDoc注释
- - **必须**为复杂组件添加功能说明
- - **必须**为关键业务逻辑添加行内注释
-
-3. **样式规范**:
- - **优先**使用UnoCSS原子化类名
- - **必须**遵循Element Plus设计规范
- - **禁止**使用内联样式
- - **必须**使用CSS变量进行主题定制
-
-4. **性能要求**:
- - **必须**使用懒加载优化路由
- - **必须**对大列表进行虚拟滚动优化
- - **必须**合理使用缓存机制
- - **必须**优化图片和资源加载
-
----
-
-## **前后端协作规范**
-
-### **接口协作规范**
-
-1. **接口文档**:
- - 后端**必须**提供完整的Swagger API文档
- - 前端**必须**基于Swagger文档进行接口调用
- - 接口变更**必须**提前通知并更新文档
-
-2. **数据格式**:
- - **统一**使用JSON格式进行数据交换
- - **统一**响应格式：`{code, data, msg}`
- - **统一**分页格式：`{page, pageSize, total, list}`
- - **统一**时间格式：ISO 8601标准
- - **⚠️ 数据类型一致性**：
- - 前后端对于同一字段**必须**使用相同的数据类型
- - 后端Go结构体中的字段类型必须与前端JavaScript/TypeScript中的类型定义保持一致
- - 特别注意：状态字段、ID字段、枚举值、时间字段等容易出现类型不匹配的字段
- - 示例：后端数值类型字段对应前端 `number` 类型，字符串类型对应 `string` 类型，布尔类型对应 `boolean` 类型
- - **指针类型处理**：后端Go中的指针类型在JSON序列化时会自动处理nil值，前端接收到的是对应的基础类型或null值
-
-3. **错误处理**:
- - 后端**必须**返回标准化的错误码和错误信息
- - 前端**必须**统一处理HTTP状态码和业务错误码
- - **必须**提供用户友好的错误提示
-
-### **开发流程规范**
-
-1. **需求分析阶段**:
- - 确定功能需求和接口设计
- - 定义数据模型和业务流程
- - 制定前后端开发计划
-
-2. **开发阶段**:
- - 后端优先开发API接口
- - 前端基于Mock数据进行并行开发
- - 定期进行接口联调测试
-
-3. **测试阶段**:
- - 单元测试：前后端各自负责
- - 集成测试：前后端协作完成
- - 用户验收测试：产品团队主导
-
-### **版本管理规范**
-
-1. **分支策略**:
- - `main`：生产环境分支
- - `develop`：开发环境分支
- - `feature/*`：功能开发分支
- - `hotfix/*`：紧急修复分支
-
-2. **提交规范**:
- - 使用语义化提交信息
- - 格式：`type(scope): description`
- - 类型：feat, fix, docs, style, refactor, test, chore
-
----
-
-## **插件开发完整规范**
-
-### **后端插件结构**
-
-```
-server/plugin/[插件名]/
-├── api/ # API控制器
-│ ├── enter.go # API组入口
-│ └── [模块].go # 具体API实现
-├── config/ # 插件配置
-│ └── config.go
-├── initialize/ # 初始化模块
-│ ├── api.go # API注册
-│ ├── gorm.go # 数据库初始化
-│ ├── menu.go # 菜单初始化
-│ ├── router.go # 路由初始化
-│ └── viper.go # 配置初始化
-├── model/ # 数据模型
-│ ├── [模型].go # 数据库模型
-│ └── request/ # 请求模型
-├── router/ # 路由定义
-│ ├── enter.go # 路由组入口
-│ └── [模块].go # 具体路由
-├── service/ # 业务服务
-│ ├── enter.go # 服务组入口
-│ └── [模块].go # 具体服务
-└── plugin.go # 插件入口
-```
-
-### **前端插件结构**
-
-```
-web/src/plugin/[插件名]/
-├── api/ # API接口
-│ └── [模块].js
-├── components/ # 插件组件
-│ └── [组件].vue
-├── view/ # 插件页面
-│ └── [页面].vue
-├── form/ # 表单组件
-│ └── [表单].vue
-└── config.js # 插件配置
-```
-
-### **插件开发工作流**
-
-1. **【第一步】需求分析**:
- - 明确插件功能和业务需求
- - 设计数据模型和接口规范
- - 规划前端页面和交互流程
-
-2. **【第二步】后端开发**:
- - 创建数据模型和请求模型
- - 实现服务层业务逻辑
- - 开发API控制器和路由
- - 编写初始化和配置代码
-
-3. **【第三步】前端开发**:
- - 创建API接口封装
- - 开发页面组件和表单
- - 实现业务逻辑和状态管理
- - 集成到主系统菜单
-
-4. **【第四步】测试集成**:
- - 单元测试和集成测试
- - 前后端联调测试
- - 用户体验测试
- - 性能和安全测试
-
-### **插件质量标准**
-
-1. **功能完整性**: 插件功能完整，满足业务需求
-2. **代码质量**: 代码规范，注释完整，易于维护
-3. **数据类型一致性**: 前后端数据模型字段类型保持严格一致，避免类型转换错误
-4. **性能表现**: 响应速度快，资源占用合理
-5. **用户体验**: 界面友好，操作流畅，错误处理完善
-6. **兼容性**: 与主系统兼容，不影响其他功能
-7. **安全性**: 数据安全，权限控制，防止安全漏洞
-
----
-
-### **建议和方案**
-
-基于以上规范，建议AI在开发gin-vue-admin项目时：
-
-1. **严格遵循分层架构**：确保前后端代码都按照规定的层次结构组织
-2. **保持代码一致性**：使用统一的命名规范、注释格式和代码风格
-3. **注重文档完整性**：确保API文档、代码注释和使用说明的完整性
-4. **优化用户体验**：关注页面加载速度、交互流畅性和错误处理
-5. **考虑扩展性**：设计时预留扩展接口，便于后续功能增强
-6. **重视安全性**：实现完善的权限控制和数据验证机制
\ No newline at end of file
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
deleted file mode 100644
index bcd5c45e..00000000
--- a/CODE_OF_CONDUCT.md
+++ /dev/null
@@ -1,76 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, sex characteristics, gender identity and expression,
-level of experience, education, socio-economic status, nationality, personal
-appearance, race, religion, or sexual identity and orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
- advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
- address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
- professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at 303176530@qq.com. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
-
-[homepage]: https://www.contributor-covenant.org
-
-For answers to common questions about this code of conduct, see
-https://www.contributor-covenant.org/faq
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
deleted file mode 100644
index b3076b25..00000000
--- a/CONTRIBUTING.md
+++ /dev/null
@@ -1,19 +0,0 @@
-
-### Contributing Guide
-#### 1 Issue Guidelines
-
-- Issues are exclusively for bug reports, feature requests and design-related topics. Other questions may be closed directly. If any questions come up when you are using Element, please hit [Gitter](https://gitter.im/element-en/Lobby) for help.
-
-- Before submitting an issue, please check if similar problems have already been issued.
-
-#### 2 Pull Request Guidelines
-
-- Fork this repository to your own account. Do not create branches here.
-
-- Commit info should be formatted as `[File Name]: Info about commit.` (e.g. `README.md: Fix xxx bug`)
-
-- Make sure PRs are created to `develop` branch instead of `master` branch.
-
-- If your PR fixes a bug, please provide a description about the related bug.
-
-- Merging a PR takes two maintainers: one approves the changes after reviewing, and then the other reviews and merges.
diff --git a/LICENSE b/LICENSE
deleted file mode 100644
index e0dca2e4..00000000
--- 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 2019 北京翻转极光科技有限责任公司
-
- 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/Makefile b/Makefile
deleted file mode 100644
index 9135c9ad..00000000
--- a/Makefile
+++ /dev/null
@@ -1,75 +0,0 @@
-SHELL = /bin/bash
-
-#SCRIPT_DIR = $(shell pwd)/etc/script
-#请选择golang版本
-BUILD_IMAGE_SERVER = golang:1.22
-#请选择node版本
-BUILD_IMAGE_WEB = node:20
-#项目名称
-PROJECT_NAME = github.com/flipped-aurora/gin-vue-admin/server
-#配置文件目录
-CONFIG_FILE = config.yaml
-#镜像仓库命名空间
-IMAGE_NAME = gva
-#镜像地址
-REPOSITORY = registry.cn-hangzhou.aliyuncs.com/${IMAGE_NAME}
-#镜像版本
-TAGS_OPT ?= latest
-PLUGIN ?= email
-
-#容器环境前后端共同打包
-build: build-web build-server
- docker run --name build-local --rm -v $(shell pwd):/go/src/${PROJECT_NAME} -w /go/src/${PROJECT_NAME} ${BUILD_IMAGE_SERVER} make build-local
-
-#容器环境打包前端
-build-web:
- docker run --name build-web-local --rm -v $(shell pwd):/go/src/${PROJECT_NAME} -w /go/src/${PROJECT_NAME} ${BUILD_IMAGE_WEB} make build-web-local
-
-#容器环境打包后端
-build-server:
- docker run --name build-server-local --rm -v $(shell pwd):/go/src/${PROJECT_NAME} -w /go/src/${PROJECT_NAME} ${BUILD_IMAGE_SERVER} make build-server-local
-
-#构建web镜像
-build-image-web:
- @cd web/ && docker build -t ${REPOSITORY}/web:${TAGS_OPT} .
-
-#构建server镜像
-build-image-server:
- @cd server/ && docker build -t ${REPOSITORY}/server:${TAGS_OPT} .
-
-#本地环境打包前后端
-build-local:
- if [ -d "build" ];then rm -rf build; else echo "OK!"; fi \
- && if [ -f "/.dockerenv" ];then echo "OK!"; else make build-web-local && make build-server-local; fi \
- && mkdir build && cp -r web/dist build/ && cp server/server build/ && cp -r server/resource build/resource
-
-#本地环境打包前端
-build-web-local:
- @cd web/ && if [ -d "dist" ];then rm -rf dist; else echo "OK!"; fi \
- && yarn config set registry http://mirrors.cloud.tencent.com/npm/ && yarn install && yarn build
-
-#本地环境打包后端
-build-server-local:
- @cd server/ && if [ -f "server" ];then rm -rf server; else echo "OK!"; fi \
- && go env -w GO111MODULE=on && go env -w GOPROXY=https://goproxy.cn,direct \
- && go env -w CGO_ENABLED=0 && go env && go mod tidy \
- && go build -ldflags "-B 0x$(shell head -c20 /dev/urandom|od -An -tx1|tr -d ' \n') -X main.Version=${TAGS_OPT}" -v
-
-#打包前后端二合一镜像
-image: build
- docker build -t ${REPOSITORY}/gin-vue-admin:${TAGS_OPT} -f deploy/docker/Dockerfile .
-
-#尝鲜版
-images: build build-image-web build-image-server
- docker build -t ${REPOSITORY}/all:${TAGS_OPT} -f deploy/docker/Dockerfile .
-
-#swagger 文档生成
-doc:
- @cd server && swag init
-
-#插件快捷打包： make plugin PLUGIN="这里是插件文件夹名称,默认为email"
-plugin:
- if [ -d ".plugin" ];then rm -rf .plugin ; else echo "OK!"; fi && mkdir -p .plugin/${PLUGIN}/{server/plugin,web/plugin} \
- && if [ -d "server/plugin/${PLUGIN}" ];then cp -r server/plugin/${PLUGIN} .plugin/${PLUGIN}/server/plugin/ ; else echo "OK!"; fi \
- && if [ -d "web/src/plugin/${PLUGIN}" ];then cp -r web/src/plugin/${PLUGIN} .plugin/${PLUGIN}/web/plugin/ ; else echo "OK!"; fi \
- && cd .plugin && zip -r ${PLUGIN}.zip ${PLUGIN} && mv ${PLUGIN}.zip ../ && cd ..
diff --git a/README-en.md b/README-en.md
deleted file mode 100644
index 3c5a8178..00000000
--- a/README-en.md
+++ /dev/null
@@ -1,317 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-English | [简体中文](./README.md)
-
-[gitee](https://gitee.com/pixelmax/gin-vue-admin): https://gitee.com/pixelmax/gin-vue-admin
-
-[github](https://github.com/flipped-aurora/gin-vue-admin): https://github.com/flipped-aurora/gin-vue-admin
-
-# Project Guidelines
-[Online Documentation](https://www.gin-vue-admin.com/) : https://www.gin-vue-admin.com/
-
-[From the environment to the deployment of teaching videos](https://www.bilibili.com/video/BV1fV411y7dT)
-
-[Development Steps](https://www.gin-vue-admin.com/guide/start-quickly/env.html) (Contributor: LLemonGreen And Fann)
-
-## 1. Basic Introduction
-
-### 1.1 Project Introduction
-
-> Gin-vue-admin is a backstage management system based on [vue](https://vuejs.org) and [gin](https://gin-gonic.com), which separates the front and rear of the full stack. It integrates jwt authentication, dynamic routing, dynamic menu, casbin authentication, form generator, code generator and other functions. It provides a variety of sample files, allowing you to focus more time on business development.
-
-[Online Demo](http://demo.gin-vue-admin.com): http://demo.gin-vue-admin.com
-
-username：admin
-
-password：123456
-
-### 1.2 Contributing Guide
-
-Hi! Thank you for choosing gin-vue-admin.
-
-Gin-vue-admin is a full-stack (frontend and backend separation) framework for developers, designers and product managers.
-
-We are excited that you are interested in contributing to gin-vue-admin. Before submitting your contribution though, please make sure to take a moment and read through the following guidelines.
-
-#### 1.2.1 Issue Guidelines
-
-- Issues are exclusively for bug reports, feature requests and design-related topics. Other questions may be closed directly. If any questions come up when you are using Element, please hit [Gitter](https://gitter.im/element-en/Lobby) for help.
-
-- Before submitting an issue, please check if similar problems have already been issued.
-
-#### 1.2.2 Pull Request Guidelines
-
-- Fork this repository to your own account. Do not create branches here.
-
-- Commit info should be formatted as `[File Name]: Info about commit.` (e.g. `README.md: Fix xxx bug`)
-
-- Make sure PRs are created to `develop` branch instead of `master` branch.
-
-- If your PR fixes a bug, please provide a description about the related bug.
-
-- Merging a PR takes two maintainers: one approves the changes after reviewing, and then the other reviews and merges.
-
-### 1.3 Version list
-
-- master: 2.0 code, for prod
-- develop: 2.0 dev code, for test
-- [gin-vue-admin_v2_dev](https://github.com/flipped-aurora/gin-vue-admin/tree/gin-vue-admin_v2_dev) (v2.0 [GormV1](https://v1.gorm.io) Stable branch)
-- [gva_gormv2_dev](https://github.com/flipped-aurora/gin-vue-admin/tree/gva_gormv2_dev) (v2.0 [GormV2](https://v2.gorm.io) Development branch)
-
-## 2. Getting started
-
-```
-- node version > v8.6.0
-- golang version >= v1.14
-- IDE recommendation: Goland
-- initialization project: different versions of the database are not initialized. See synonyms at initialization https://www.gin-vue-admin.com/docs/first
-- Replace the Qiniuyun public key, private key, warehouse name and default url address in the project to avoid data confusion in the test file.
-```
-
-### 2.1 server project
-
-use `Goland` And other editing tools，open server catalogue，You can't open it. `gin-vue-admin` root directory
-
-```bash
-# clone the project
-git clone https://github.com/flipped-aurora/gin-vue-admin.git
-
-# open server catalogue
-cd server
-
-# use go mod And install the go dependency package
-go generate
-
-# Compile
-go build -o server main.go (windows the compile command is go build -o server.exe main.go )
-
-# Run binary
-./server (windows The run command is server.exe)
-```
-
-### 2.1 web project
-
-```bash
-# enter the project directory
-cd web
-
-# install dependency
-npm install
-
-# develop
-npm run serve
-```
-
-### 2.2 Server
-
-```bash
-# using go.mod
-
-# install go modules
-go list (go mod tidy)
-
-# build the server
-go build
-```
-
-### 2.3 API docs auto-generation using swagger
-
-#### 2.3.1 install swagger
-
-##### (1) Using VPN or outside mainland China
-````
-go get -u github.com/swaggo/swag/cmd/swag
-````
-
-##### (2) In mainland China
-
-In mainland China, access to go.org/x is prohibited，we recommend [goproxy.io](https://goproxy.io/zh/) or [goproxy.cn](https://goproxy.cn)
-
-````bash
-# If you are using a version of Go 1.13 - 1.15 Need to set up manually GO111MODULE=on, The opening mode is as follows, If your Go version is 1.16 ~ Latest edition You can ignore the following step one
-# Step one、Enable Go Modules Function
-go env -w GO111MODULE=on
-# Step two、Configuration GOPROXY Environment variable
-go env -w GOPROXY=https://goproxy.cn,https://goproxy.io,direct
-
-# If you dislike trouble,You can use the go generate Automatically execute code before compilation, But this can't be used command line terminal of `Goland` or `Vscode`
-cd server
-go generate -run "go env -w .*?"
-
-# 使用如下命令下载swag
-go get -u github.com/swaggo/swag/cmd/swag
-````
-
-#### 2.3.2 API docs generation
-
-````
-cd server
-swag init
-````
-
-> After executing the above command，server directory will appear in the docs folder `docs.go`, `swagger.json`, `swagger.yaml` Three file updates，After starting the go service, type in the browser [http://localhost:8888/swagger/index.html](http://localhost:8888/swagger/index.html) You can view swagger document
-
-
-## 3. Technical selection
-
-- Frontend: using [Element](https://github.com/ElemeFE/element) based on [Vue](https://vuejs.org)，to code the page.
-- Backend: using [Gin](https://gin-gonic.com/) to quickly build basic RESTful API. [Gin](https://gin-gonic.com/)is a web framework written in Go (Golang).
-- DB: `MySql`(5.6.44)，using [gorm](http://gorm.io)` to implement data manipulation, added support for SQLite databases.
-- Cache: using `Redis` to implement the recording of the JWT token of the currently active user and implement the multi-login restriction.
-- API: using Swagger to auto generate APIs docs。
-- Config: using [fsnotify](https://github.com/fsnotify/fsnotify) and [viper](https://github.com/spf13/viper) to implement `yaml` config file。
-- Log: using [zap](https://github.com/uber-go/zap) record logs。
-
-## 4. Project Architecture
-
-### 4.1 Architecture Diagram
-
-
-
-### 4.2 Front-end Detailed Design Diagram (Contributor: baobeisuper)
-
-
-
-### 4.3 Project Layout
-
-```
- ├── server
- ├── api (api entrance)
- │ └── v1 (v1 version interface)
- ├── config (configuration package)
- ├── core (core document)
- ├── docs (swagger document directory)
- ├── global (global object)
- ├── initialize (initialization)
- │ └── internal (initialize internal function)
- ├── middleware (middleware layer)
- ├── model (model layer)
- │ ├── request (input parameter structure)
- │ └── response (out-of-parameter structure)
- ├── packfile (static file packaging)
- ├── resource (static resource folder)
- │ ├── excel (excel import and export default path)
- │ ├── page (form generator)
- │ └── template (template)
- ├── router (routing layer)
- ├── service (service layer)
- ├── source (source layer)
- └── utils (tool kit)
- ├── timer (timer interface encapsulation)
- └── upload (oss interface encapsulation)
-
- └─web （frontend）
- ├─public （deploy templates）
- └─src （source code）
- ├─api （frontend APIs）
- ├─assets （static files）
- ├─components（components）
- ├─router （frontend routers）
- ├─store （vuex state management）
- ├─style （common styles）
- ├─utils （frontend common utilitie）
- └─view （pages）
-
-```
-
-## 5. Features
-
-- Authority management: Authority management based on `jwt` and `casbin`.
-- File upload and download: implement file upload operations based on `Qiniuyun', `Aliyun 'and `Tencent Cloud` (please develop your own application for each platform corresponding to `token` or `key` ).
-- Pagination Encapsulation：The frontend uses `mixins` to encapsulate paging, and the paging method can call `mixins` .
-- User management: The system administrator assigns user roles and role permissions.
-- Role management: Create the main object of permission control, and then assign different API permissions and menu permissions to the role.
-- Menu management: User dynamic menu configuration implementation, assigning different menus to different roles.
-- API management: Different users can call different API permissions.
-- Configuration management: the configuration file can be modified in the foreground (this feature is not available in the online experience site).
-- Conditional search: Add an example of conditional search.
-- Restful example: You can see sample APIs in user management module.
- - Front-end file reference: [web/src/view/superAdmin/api/api.vue](https://github.com/flipped-aurora/gin-vue-admin/blob/master/web/src/view/superAdmin/api/api.vue).
- - Stage reference: [server/router/sys_api.go](https://github.com/flipped-aurora/gin-vue-admin/blob/master/server/router/sys_api.go).
-- Multi-login restriction: Change `user-multipoint` to true in `system` in `config.yaml` (You need to configure redis and redis parameters yourself. During the test period, please report in time if there is a bug).
-- Upload file by chunk：Provides examples of file upload and large file upload by chunk.
-- Form Builder：With the help of [@form-generator](https://github.com/JakHuang/form-generator).
-- Code generator: Providing backend with basic logic and simple curd code generator.
-
-## 6. Knowledge base
-
-### 6.1 Team blog
-
-> https://www.yuque.com/flipped-aurora
->
->There are video courses about frontend framework in our blo. If you think the project is helpful to you, you can add my personal WeChat:shouzi_1994，your comments is welcomed。
-
-### 6.2 Video courses
-
-(1) Development environment course
-
-> Bilibili：https://www.bilibili.com/video/BV1Fg4y187Bw/
-
-(2) Template course
-
-> Bilibili：https://www.bilibili.com/video/BV16K4y1r7BD/
-
-(3) 2.0 version introduction and development experience
-
-> Bilibili：https://www.bilibili.com/video/BV1aV411d7Gm#reply2831798461
-
-(4) Golang basic course
-
-> https://space.bilibili.com/322210472/channel/detail?cid=108884
-
-(5) gin frame basic teaching
-
-> bilibili：https://space.bilibili.com/322210472/channel/detail?cid=126418&ctype=0
-
-(6) gin-vue-admin version update introduction video
-> bilibili：https://space.bilibili.com/322210472/channel/detail?cid=126418&ctype=0
-
-## 7.Contacts
-
-### 7.1 Groups
-
-#### QQ group: 622360840
-
-| QQ group |d
-| :---: |
-|
-
-
-
-
-
|
-
-
-#### Wechat group: comment "加入gin-vue-admin交流群"
-
-| Wechat |
-| :---: |
-| 
-
-#### [About Us](https://www.gin-vue-admin.com/about/join.html)
-
-## 8. Contributors
-
-Thank you for considering your contribution to gin-vue-admin!
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-[English](./README-en.md) | 简体中文
-
-## ✨一分钟生成前后端基础代码
-
-|
-
- 📄 创建基础模板 -🤖 AI生成结构 -⏰ 生成代码 -🏷️ 分配权限 -🎉 基础CURD生成完成 - |
- - - | -
-
-
-
-## 1. 基本介绍
-
-### 1.1 项目介绍
-
-> Gin-vue-admin是一个基于 [vue](https://vuejs.org) 和 [gin](https://gin-gonic.com) 开发的全栈前后端分离的开发基础平台，集成jwt鉴权，动态路由，动态菜单，casbin鉴权，表单生成器，代码生成器等功能，提供多种示例文件，让您把更多时间专注在业务开发上。
-
-[在线预览](http://demo.gin-vue-admin.com): http://demo.gin-vue-admin.com
-
-测试用户名：admin
-
-测试密码：123456
-
-### 1.2 贡献指南
-Hi! 首先感谢你使用 gin-vue-admin。
-
-Gin-vue-admin 是一套为快速研发准备的一整套前后端分离架构式的开源框架，旨在快速搭建中小型项目。
-
-Gin-vue-admin 的成长离不开大家的支持，如果你愿意为 gin-vue-admin 贡献代码或提供建议，请阅读以下内容。
-
-#### 1.2.1 Issue 规范
-- issue 仅用于提交 Bug 或 Feature 以及设计相关的内容，其它内容可能会被直接关闭。
-
-- 在提交 issue 之前，请搜索相关内容是否已被提出。
-
-#### 1.2.2 Pull Request 规范
-- 请先 fork 一份到自己的项目下，不要直接在仓库下建分支。
-
-- commit 信息要以`[文件名]: 描述信息` 的形式填写，例如 `README.md: fix xxx bug`。
-
-- 如果是修复 bug，请在 PR 中给出描述信息。
-
-- 合并代码需要两名维护人员参与：一人进行 review 后 approve，另一人再次 review，通过后即可合并。
-
-## 2. 使用说明
-
-```
-- node版本 > v18.16.0
-- golang版本 >= v1.22
-- IDE推荐：Goland
-```
-
-### 2.1 server项目
-
-使用 `Goland` 等编辑工具，打开server目录，不可以打开 gin-vue-admin 根目录
-
-```bash
-
-# 克隆项目
-git clone https://github.com/flipped-aurora/gin-vue-admin.git
-# 进入server文件夹
-cd server
-
-# 使用 go mod 并安装go依赖包
-go generate
-
-# 运行
-go run .
-
-```
-
-### 2.2 web项目
-
-```bash
-# 进入web文件夹
-cd web
-
-# 安装依赖
-npm install
-
-# 启动web项目
-npm run serve
-```
-
-### 2.3 swagger自动化API文档
-
-#### 2.3.1 安装 swagger
-
-``` shell
-go install github.com/swaggo/swag/cmd/swag@latest
-```
-
-#### 2.3.2 生成API文档
-
-```` shell
-cd server
-swag init
-````
-
-> 执行上面的命令后，server目录下会出现docs文件夹里的 `docs.go`, `swagger.json`, `swagger.yaml` 三个文件更新，启动go服务之后, 在浏览器输入 [http://localhost:8888/swagger/index.html](http://localhost:8888/swagger/index.html) 即可查看swagger文档
-
-### 2.4 VSCode工作区
-
-#### 2.4.1 开发
-
-使用`VSCode`打开根目录下的工作区文件`gin-vue-admin.code-workspace`，在边栏可以看到三个虚拟目录：`backend`、`frontend`、`root`。
-
-#### 2.4.2 运行/调试
-
-在运行和调试中也可以看到三个task：`Backend`、`Frontend`、`Both (Backend & Frontend)`。运行`Both (Backend & Frontend)`可以同时启动前后端项目。
-
-#### 2.4.3 settings
-
-在工作区配置文件中有`go.toolsEnvVars`字段，是用于`VSCode`自身的go工具环境变量。此外在多go版本的系统中，可以通过`gopath`、`go.goroot`指定运行版本。
-
-```json
- "go.gopath": null,
- "go.goroot": null,
-```
-
-## 3. 技术选型
-
-- 前端：用基于 [Vue](https://vuejs.org) 的 [Element](https://github.com/ElemeFE/element) 构建基础页面。
-- 后端：用 [Gin](https://gin-gonic.com/) 快速搭建基础restful风格API，[Gin](https://gin-gonic.com/) 是一个go语言编写的Web框架。
-- 数据库：采用`MySql` > (5.7) 版本 数据库引擎 InnoDB，使用 [gorm](http://gorm.cn) 实现对数据库的基本操作。
-- 缓存：使用`Redis`实现记录当前活跃用户的`jwt`令牌并实现多点登录限制。
-- API文档：使用`Swagger`构建自动化文档。
-- 配置文件：使用 [fsnotify](https://github.com/fsnotify/fsnotify) 和 [viper](https://github.com/spf13/viper) 实现`yaml`格式的配置文件。
-- 日志：使用 [zap](https://github.com/uber-go/zap) 实现日志记录。
-
-## 4. 项目架构
-
-### 4.1 系统架构图
-
-
-
-### 4.2 前端详细设计图 （提供者:baobeisuper）
-
-
-
-### 4.3 目录结构
-
-```
- ├── server
- ├── api (api层)
- │ └── v1 (v1版本接口)
- ├── config (配置包)
- ├── core (核心文件)
- ├── docs (swagger文档目录)
- ├── global (全局对象)
- ├── initialize (初始化)
- │ └── internal (初始化内部函数)
- ├── middleware (中间件层)
- ├── model (模型层)
- │ ├── request (入参结构体)
- │ └── response (出参结构体)
- ├── packfile (静态文件打包)
- ├── resource (静态资源文件夹)
- │ ├── excel (excel导入导出默认路径)
- │ ├── page (表单生成器)
- │ └── template (模板)
- ├── router (路由层)
- ├── service (service层)
- ├── source (source层)
- └── utils (工具包)
- ├── timer (定时器接口封装)
- └── upload (oss接口封装)
-
- web
- ├── babel.config.js
- ├── Dockerfile
- ├── favicon.ico
- ├── index.html -- 主页面
- ├── limit.js -- 助手代码
- ├── package.json -- 包管理器代码
- ├── src -- 源代码
- │ ├── api -- api 组
- │ ├── App.vue -- 主页面
- │ ├── assets -- 静态资源
- │ ├── components -- 全局组件
- │ ├── core -- gva 组件包
- │ │ ├── config.js -- gva网站配置文件
- │ │ ├── gin-vue-admin.js -- 注册欢迎文件
- │ │ └── global.js -- 统一导入文件
- │ ├── directive -- v-auth 注册文件
- │ ├── main.js -- 主文件
- │ ├── permission.js -- 路由中间件
- │ ├── pinia -- pinia 状态管理器，取代vuex
- │ │ ├── index.js -- 入口文件
- │ │ └── modules -- modules
- │ │ ├── dictionary.js
- │ │ ├── router.js
- │ │ └── user.js
- │ ├── router -- 路由声明文件
- │ │ └── index.js
- │ ├── style -- 全局样式
- │ │ ├── base.scss
- │ │ ├── basics.scss
- │ │ ├── element_visiable.scss -- 此处可以全局覆盖 element-plus 样式
- │ │ ├── iconfont.css -- 顶部几个icon的样式文件
- │ │ ├── main.scss
- │ │ ├── mobile.scss
- │ │ └── newLogin.scss
- │ ├── utils -- 方法包库
- │ │ ├── asyncRouter.js -- 动态路由相关
- │ │ ├── btnAuth.js -- 动态权限按钮相关
- │ │ ├── bus.js -- 全局mitt声明文件
- │ │ ├── date.js -- 日期相关
- │ │ ├── dictionary.js -- 获取字典方法
- │ │ ├── downloadImg.js -- 下载图片方法
- │ │ ├── format.js -- 格式整理相关
- │ │ ├── image.js -- 图片相关方法
- │ │ ├── page.js -- 设置页面标题
- │ │ ├── request.js -- 请求
- │ │ └── stringFun.js -- 字符串文件
- | ├── view -- 主要view代码
- | | ├── about -- 关于我们
- | | ├── dashboard -- 面板
- | | ├── error -- 错误
- | | ├── example --上传案例
- | | ├── iconList -- icon列表
- | | ├── init -- 初始化数据
- | | | ├── index -- 新版本
- | | | ├── init -- 旧版本
- | | ├── layout -- layout约束页面
- | | | ├── aside
- | | | ├── bottomInfo -- bottomInfo
- | | | ├── screenfull -- 全屏设置
- | | | ├── setting -- 系统设置
- | | | └── index.vue -- base 约束
- | | ├── login --登录
- | | ├── person --个人中心
- | | ├── superAdmin -- 超级管理员操作
- | | ├── system -- 系统检测页面
- | | ├── systemTools -- 系统配置相关页面
- | | └── routerHolder.vue -- page 入口页面
- ├── vite.config.js -- vite 配置文件
- └── yarn.lock
-
-```
-
-## 5. 主要功能
-
-- 权限管理：基于`jwt`和`casbin`实现的权限管理。
-- 文件上传下载：实现基于`七牛云`, `阿里云`, `腾讯云` 的文件上传操作(请开发自己去各个平台的申请对应 `token` 或者对应`key`)。
-- 分页封装：前端使用 `mixins` 封装分页，分页方法调用 `mixins` 即可。
-- 用户管理：系统管理员分配用户角色和角色权限。
-- 角色管理：创建权限控制的主要对象，可以给角色分配不同api权限和菜单权限。
-- 菜单管理：实现用户动态菜单配置，实现不同角色不同菜单。
-- api管理：不同用户可调用的api接口的权限不同。
-- 配置管理：配置文件可前台修改(在线体验站点不开放此功能)。
-- 条件搜索：增加条件搜索示例。
-- restful示例：可以参考用户管理模块中的示例API。
- - 前端文件参考: [web/src/view/superAdmin/api/api.vue](https://github.com/flipped-aurora/gin-vue-admin/blob/master/web/src/view/superAdmin/api/api.vue)
- - 后台文件参考: [server/router/sys_api.go](https://github.com/flipped-aurora/gin-vue-admin/blob/master/server/router/sys_api.go)
-- 多点登录限制：需要在`config.yaml`中把`system`中的`use-multipoint`修改为true(需要自行配置Redis和Config中的Redis参数，测试阶段，有bug请及时反馈)。
-- 分片上传：提供文件分片上传和大文件分片上传功能示例。
-- 表单生成器：表单生成器借助 [@Variant Form](https://github.com/vform666/variant-form) 。
-- 代码生成器：后台基础逻辑以及简单curd的代码生成器。
-
-## 6. 知识库
-
-## 6.1 团队博客
-
-> https://www.yuque.com/flipped-aurora
->
->内有前端框架教学视频。如果觉得项目对您有所帮助可以添加我的个人微信:shouzi_1994，欢迎您提出宝贵的需求。
-
-## 6.2 教学视频
-
-（1）手把手教学视频
-
-> https://www.bilibili.com/video/BV1Rg411u7xH/
-
-（2）后端目录结构调整介绍以及使用方法
-
-> https://www.bilibili.com/video/BV1x44y117TT/
-
-（3）golang基础教学视频
-
-> bilibili：https://space.bilibili.com/322210472/channel/detail?cid=108884
-
-（4）gin框架基础教学
-
-> bilibili：https://space.bilibili.com/322210472/channel/detail?cid=126418&ctype=0
-
-（5）gin-vue-admin 版本更新介绍视频
-
-> bilibili：https://www.bilibili.com/video/BV1kv4y1g7nT
-
-## 7. 联系方式
-
-### 7.1 技术群
-
-### QQ交流群：971857775
-
-### 微信交流群
-| 微信 |
-| :---: |
-|
-
-防止广告进群，添加微信，输入以下代码执行结果（请勿转码为string）
-
-```
-str := "5Yqg5YWlR1ZB5Lqk5rWB576k"
-decodeBytes, err := base64.StdEncoding.DecodeString(str)
-fmt.Println(decodeBytes, err)
-```
-
-### [关于我们](https://www.gin-vue-admin.com/about/join.html)
-
-## 8. 贡献者
-
-感谢您对gin-vue-admin的贡献!
-
-
-