You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

284 lines
11 KiB

5 years ago
4 years ago
4 years ago
4 years ago
5 years ago
5 years ago
5 years ago
5 years ago
5 years ago
4 years ago
5 years ago
5 years ago
5 years ago
5 years ago
5 years ago
5 years ago
5 years ago
5 years ago
5 years ago
5 years ago
5 years ago
5 years ago
5 years ago
5 years ago
5 years ago
5 years ago
5 years ago
5 years ago
4 years ago
5 years ago
4 years ago
  1. 
  2. <div align=center>
  3. <img src="http://qmplusimg.henrongyi.top/gvalogo.jpg" width=300" height="300" />
  4. </div>
  5. <div align=center>
  6. <img src="https://img.shields.io/badge/golang-1.12-blue"/>
  7. <img src="https://img.shields.io/badge/gin-1.4.0-lightBlue"/>
  8. <img src="https://img.shields.io/badge/vue-2.6.10-brightgreen"/>
  9. <img src="https://img.shields.io/badge/element--ui-2.12.0-green"/>
  10. <img src="https://img.shields.io/badge/gorm-1.9.12-red"/>
  11. </div>
  12. English | [简体中文](./README-zh_CN.md)
  13. # Project Guidelines
  14. [Online Documentation](http://doc.henrongyi.top/)
  15. [Development Steps](http://doc.henrongyi.top/help/) (Contributor: <a href="https://github.com/LLemonGreen">LLemonGreen</a> And <a href="https://github.com/fkk0509">Fann</a>)
  16. - Web UI Framework:[element-ui](https://github.com/ElemeFE/element)
  17. - Server Framework:[gin](https://github.com/gin-gonic/gin)
  18. ## 1. Basic Introduction
  19. ### 1.1 Project Introduction
  20. [Online Demo](http://demo.gin-vue-admin.com/)
  21. username:admin
  22. password:123456
  23. > Gin-vue-admin is a full-stack (frontend and backend separation) framework designed for management system.
  24. > It integrates multiple functions, such as JWT authentication, dynamic routing, dynamic menu, casbin authentication, form generator, code generator, etc. So that you can focus more time on your business Requirements.
  25. Hi! Thank you for choosing gin-vue-admin.
  26. Gin-vue-admin is a full-stack (frontend and backend separation) framework for developers, designers and product managers.
  27. 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.
  28. ### 1.2 Contributing Guide
  29. #### 1.2.1 Issue Guidelines
  30. - 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.
  31. - Before submitting an issue, please check if similar problems have already been issued.
  32. #### 1.2.2 Pull Request Guidelines
  33. - Fork this repository to your own account. Do not create branches here.
  34. - Commit info should be formatted as `[File Name]: Info about commit.` (e.g. `README.md: Fix xxx bug`)
  35. - <font color=red>Make sure PRs are created to `develop` branch instead of `master` branch.</font>
  36. - If your PR fixes a bug, please provide a description about the related bug.
  37. - Merging a PR takes two maintainers: one approves the changes after reviewing, and then the other reviews and merges.
  38. ### 1.3 Version list
  39. - master: 2.0 code, for prod
  40. - develop: 2.0 dev code, for test
  41. - [gin-vue-admin_v2.0_dev](https://github.com/flipped-aurora/gin-vue-admin/tree/gin-vue-admin_v2_dev) (v2.0 is no longer compatible with v1.0)
  42. - [gin-vue-admin_v1.0_stable](https://github.com/flipped-aurora/gin-vue-admin/tree/gin-vue-admin_v1_stable) (stop maintenance)
  43. - [gin-vue-admin_v1.0_dev](https://github.com/flipped-aurora/gin-vue-admin/tree/gin-vue-admin_v1_dev) (stop maintenance)
  44. ## 2. Getting started
  45. ```
  46. - node version > v8.6.0
  47. - golang version >= v1.11
  48. - IDE recommendation: Goland
  49. - After you clone the project, use the scripts in directory db to create your own database.
  50. - We recommend you to apply for your own cloud service in QINIU. Replace the public key, private key, warehouse name and default url address with your own, so as not to mess up the test database.
  51. ```
  52. ### 2.1 Web
  53. ```bash
  54. # clone the project
  55. git clone https://github.com/piexlmax/gin-vue-admin.git
  56. # enter the project directory
  57. cd web
  58. # install dependency
  59. npm install
  60. # develop
  61. npm run serve
  62. ```
  63. ### 2.2 Server
  64. ```bash
  65. # using go.mod
  66. # install go modules
  67. go list (go mod tidy)
  68. # build the server
  69. go build
  70. ```
  71. ### 2.3 API docs auto-generation using swagger
  72. #### 2.3.1 install swagger
  73. ##### (1) Using VPN or outside mainland China
  74. ````
  75. go get -u github.com/swaggo/swag/cmd/swag
  76. ````
  77. ##### (2) In mainland China
  78. In mainland China, access to go.org/x is prohibited,we recommend [goproxy.io](https://goproxy.io/zh/)
  79. ````bash
  80. If you are using Go version 1.13 and above (recommended)
  81. # Enable Go Modules function
  82. go env -w GO111MODULE=on
  83. # Configure GOPROXY environment variables
  84. go env -w GOPROXY=https://goproxy.io,direct
  85. If you are using Go version 1.12 and below
  86. go env -w GO111MODULE=on
  87. go env -w GOPROXY=https://goproxy.io
  88. # get swag
  89. go get -g -v github.com/swaggo/swag/cmd/swag
  90. # cd GOPATH/src/github.com/swaggo/swag/cmd/swag
  91. go install
  92. ````
  93. #### 2.3.2 API docs generation
  94. ````
  95. cd server
  96. swag init
  97. ````
  98. After executing the above command,`docs` will show in `server/`,then open your browser, jump into `http://localhost:8888/swagger/index.html` to see the swagger APIs.
  99. ## 3. Technical selection
  100. - Frontend: using `Element-UI` based on vue,to code the page.
  101. - Backend: using `Gin` to quickly build basic RESTful API. `Gin` is a web framework written in Go (Golang).
  102. - DB: `MySql`(5.6.44),using `gorm` to implement data manipulation, added support for SQLite databases.
  103. - Cache: using `Redis` to implement the recording of the JWT token of the currently active user and implement the multi-login restriction.
  104. - API: using Swagger to auto generate APIs docs。
  105. - Config: using `fsnotify` and `viper` to implement `yaml` config file。
  106. - Log: using `go-logging` record logs。
  107. ## 4. Project Architecture
  108. ### 4.1 Architecture Diagram
  109. ![Architecture diagram](http://qmplusimg.henrongyi.top/gva/gin-vue-admin.png)
  110. ### 4.2 Front-end Detailed Design Diagram (Contributor: <a href="https://github.com/baobeisuper">baobeisuper</a>)
  111. ![Front-end Detailed Design Diagram](http://qmplusimg.henrongyi.top/naotu.png)
  112. ### 4.3 Project Layout
  113. ```
  114. ├─server (backend)
  115. │ ├─api (API entrance)
  116. │ ├─config (config file)
  117. │ ├─core (core code)
  118. │ ├─db (db scripts)
  119. │ ├─docs (swagger APIs docs)
  120. │ ├─global (global objet)
  121. │ ├─initialiaze (initialiazation)
  122. │ ├─middleware (middle ware)
  123. │ ├─model (model and services)
  124. │ ├─resource (resources, such as static pages, templates)
  125. │ ├─router (routers)
  126. │ ├─service (services)
  127. │ └─utils (common utilities)
  128. └─web (frontend)
  129. ├─public (deploy templates)
  130. └─src (source code)
  131. ├─api (frontend APIs)
  132. ├─assets (static files)
  133. ├─components(components)
  134. ├─router (frontend routers)
  135. ├─store (vuex state management)
  136. ├─style (common styles)
  137. ├─utils (frontend common utilitie)
  138. └─view (pages)
  139. ```
  140. ## 5. Features
  141. - Authority management: Authority management based on `jwt` and `casbin`.
  142. - File upload & download: File upload operation based on Qiniu Cloud (In order to make it easier for everyone to test, I have provided various important tokens of my Qiniu test number, and I urge you not to make things a mess).
  143. - Pagination Encapsulation:The frontend uses mixins to encapsulate paging, and the paging method can call mixins
  144. - User management: The system administrator assigns user roles and role permissions.
  145. - Role management: Create the main object of permission control, and then assign different API permissions and menu permissions to the role.
  146. - Menu management: User dynamic menu configuration implementation, assigning different menus to different roles.
  147. - API management: Different users can call different API permissions.
  148. - Configuration management: The configuration file can be modified in the web page (the test environment does not provide this function).
  149. - Rich text editor: Embed MarkDown editor function.
  150. - Conditional search: Add an example of conditional search.
  151. - Restful example: You can see sample APIs in user management module.
  152. ```
  153. fontend code file: src\view\superAdmin\api\api.vue
  154. backend code file: model\dnModel\api.go
  155. ```
  156. - Multi-login restriction: Change `userMultipoint` 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).
  157. - Upload file by chunk:Provides examples of file upload and large file upload by chunk.
  158. - Form Builder:With the help of [@form-generator](https://github.com/JakHuang/form-generator).
  159. - Code generator: Providing backend with basic logic and simple curd code generator.
  160. ## 6. To-do list
  161. - [ ] upload & export Excel
  162. - [ ] e-chart
  163. - [ ] workflow, task transfer function
  164. - [ ] frontend independent mode, mock
  165. ## 7. Knowledge base
  166. ### 7.1 Team blog
  167. > https://www.yuque.com/flipped-aurora
  168. >
  169. >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。
  170. ### 7.2 Video courses
  171. (1) Development environment course
  172. > Bilibili:https://www.bilibili.com/video/BV1Fg4y187Bw/
  173. (2) Template course
  174. > Bilibili:https://www.bilibili.com/video/BV16K4y1r7BD/
  175. (3)2.0 version introduction and development experience
  176. > Bilibili:https://www.bilibili.com/video/BV1aV411d7Gm#reply2831798461
  177. (4) Golang basic course (coming soon)
  178. > https://space.bilibili.com/322210472/channel/detail?cid=108884
  179. ## 8. Contacts
  180. ### 8.1 Groups
  181. | QQ group |
  182. | :---: |
  183. | <img src="http://qmplusimg.henrongyi.top/qq.jpg" width="180"/> |
  184. ### QQ group: 622360840
  185. ### Wechat group: add anyone above, comment "加入gin-vue-admin交流群"
  186. ### 8.2 Team members
  187. | Jiang | Yin | Yan | Du | Yin | Song |
  188. | :---: | :---: | :---: | :---: | :---: | :---: |
  189. | <img width="150" src="http://qmplusimg.henrongyi.top/qrjjz.png"> | <img width="150" src="http://qmplusimg.henrongyi.top/qryx.png"> | <img width="150" src="http://qmplusimg.henrongyi.top/qryr.png"> | <img width="150" src="http://qmplusimg.henrongyi.top/qrdjl.png"> | <img width="150" src="http://qmplusimg.henrongyi.top/qrygl.png"> | <img width="150" src="http://qmplusimg.henrongyi.top/qrsong.png"> |
  190. | Nick name | Project position | First name |
  191. | ---- | ---- | ---- |
  192. | [@piexlmax](https://github.com/piexlmax) | Project sponsor | Jiang |
  193. | [@granty1](https://github.com/granty1) | Backend developer | Yin |
  194. | [@Ruio9244](https://github.com/Ruio9244) | Full-stack developer | Yan |
  195. | [@1319612909](https://github.com/1319612909) | UI developer | Du |
  196. | [@krank666](https://github.com/krank666) | Frontend developer | Yin |
  197. | [@chen-chen-up](https://github.com/chen-chen-up) | Novice developer | Song |
  198. | [@SliverHorn](https://github.com/SliverHorn) | Community Administrator | Lai |
  199. ## 9. Donate
  200. If you find this project useful, you can buy author a glass of juice :tropical_drink: [here](http://doc.henrongyi.top/more/coffee.html)
  201. ## 10. Commercial considerations
  202. If you use this project for commercial purposes, please comply with the Apache2.0 agreement and retain the author's technical support statement.