初始化
This commit is contained in:
hezhidong
@@ -1,92 +1,95 @@
|
||||
# 管理端重庆创兴佳维修微信小程序-后台管理
|
||||
#💐💐💐 Vue 3.2 + vuex + Vite2 + Element-Plus 后台管理系统
|
||||
|
||||
|
||||
|
||||
### 前言 📖
|
||||
|
||||
## Getting started
|
||||
项目基于 Vue3.2、Javascript、Vite2、vuex、Element-Plus 开发的一套后台管理模板，目前利用空余时间开发 🕒🕒🕒🕒。项目中借鉴很多优秀的后台管理系统，从 0 开始搭建项目（其中 ui 图是借鉴了【即时设计】里的优秀的设计图），整个项目还有很多地方不完善，后期会持续更新，希望大家能多提意见。
|
||||
|
||||
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
|
||||
### ？为什么开发这个管理系统 👩🔬
|
||||
|
||||
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
|
||||
- 主要是想把自己常用的组件进行一个封装 二次巩固
|
||||
- 目前看了很多优秀的 Vue3 的开源后台管理系统，感觉都非常庞大（想开发一套适合自己的）
|
||||
|
||||
## Add your files
|
||||
### 一、在线预览 🛫
|
||||
|
||||
- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
|
||||
- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
|
||||
- Link：http://124.221.156.158:9797/#/login
|
||||
|
||||
### 二、gitee 地址 🛫
|
||||
|
||||
- Link：https://gitee.com/tanzo/vue-manage-system
|
||||
|
||||
### 三、本地预览 🛫🛫🛫
|
||||
|
||||
```
|
||||
cd existing_repo
|
||||
git remote add origin http://gitlab.lzyyj.com/hzd/backstage-repair.git
|
||||
git branch -M main
|
||||
git push -uf origin main
|
||||
git clone 项目地址
|
||||
|
||||
npm install (依赖安装失败可以尝试cnpm install)
|
||||
|
||||
npm run dev
|
||||
```
|
||||
|
||||
## Integrate with your tools
|
||||
### 四、🔨 项目功能
|
||||
|
||||
- [ ] [Set up project integrations](http://gitlab.lzyyj.com/hzd/backstage-repair/-/settings/integrations)
|
||||
- 🚀 使用 Vue3.2 开发，单文件组件 `＜script setup＞`开发
|
||||
- 🚀 采用动态路由菜单模式
|
||||
- 🚀 数据模拟用到了 MockJS
|
||||
- 🚀 使用 Vuex getter 模块化管理（ 加入了持久化插件）
|
||||
- 🚀 Axios 的二次封装 （全局错误拦截、常用请求封装、全局请求 Loading、取消重复请求……）
|
||||
- 🚀 对 el-table 组件进行的二次封装
|
||||
- 🚀 使用 vue-router 进行路由权限拦截（403 页面）、页面按钮权限配置、路由懒加载
|
||||
- 🚀 使用 keep-alive 对整个页面进行缓存，支持多级嵌套页面（缓存路由里可配置、页面切换加入动画效果）
|
||||
- 🚀 常用自定义指令的封装 直接 v-copy 即可实现复制 （复制、拖拽、、、等等）
|
||||
- 🚀 vite.config.js 打包配置(静态资源合并打包/清除 log/gzip 压缩配置等)
|
||||
|
||||
## Collaborate with your team
|
||||
### 五、项目截图 📷
|
||||
|
||||
- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
|
||||
- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
|
||||
- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
|
||||
- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
|
||||
- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
|
||||
#### 1、登录页：
|
||||
|
||||
## Test and Deploy
|
||||
|
||||
|
||||
Use the built-in continuous integration in GitLab.
|
||||
#### 2、首页：
|
||||
|
||||
- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
|
||||
- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
|
||||
- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
|
||||
- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
|
||||
- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
|
||||
|
||||
|
||||
***
|
||||
#### 3、表格页：
|
||||
|
||||
# Editing this README
|
||||
|
||||
|
||||
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
|
||||
#### 4、流程图：
|
||||
|
||||
## Suggestions for a good README
|
||||
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
|
||||
|
||||
|
||||
## Name
|
||||
Choose a self-explaining name for your project.
|
||||
### 六、文件资源目录 📚
|
||||
|
||||
## Description
|
||||
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
|
||||
```text
|
||||
├─ .vscode # vscode推荐配置
|
||||
├─ public # 静态资源文件（忽略打包）
|
||||
├─ src
|
||||
│ ├─ api # API 接口管理
|
||||
│ ├─ assets # 静态资源文件
|
||||
│ ├─ components # 全局组件
|
||||
│ ├─ config # 全局配置项
|
||||
│ ├─ instruction # 指令文件
|
||||
│ ├─ layout # 框架布局
|
||||
│ ├─ router # 路由管理
|
||||
│ ├─ store # VUEX模块化管理
|
||||
│ ├─ styles # 全局样式
|
||||
│ ├─ utils # 工具库（color函数的封装）
|
||||
│ ├─ views # 项目所有页面
|
||||
│ ├─ App.vue # 入口页面
|
||||
│ └─ main.js # 入口文件
|
||||
└─ vite.config.ts # vite 配置
|
||||
```
|
||||
|
||||
## Badges
|
||||
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
|
||||
### 七、浏览器支持
|
||||
|
||||
## Visuals
|
||||
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
|
||||
> vue3.2 不支持 IE 浏览器。其他还行吧（其实我没测 🤣🧐）
|
||||
|
||||
## Installation
|
||||
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
|
||||
### 八、项目后台接口 🧩🧐
|
||||
|
||||
## Usage
|
||||
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
|
||||
> 项目后台接口全部采用 Mock 数据
|
||||
|
||||
## Support
|
||||
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
|
||||
### 九 最后求个关注 👀 🌟🌟🌟🙇♀️🙇♀️🙇♀️
|
||||
|
||||
## Roadmap
|
||||
If you have ideas for releases in the future, it is a good idea to list them in the README.
|
||||
|
||||
## Contributing
|
||||
State if you are open to contributions and what your requirements are for accepting them.
|
||||
|
||||
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
|
||||
|
||||
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
|
||||
|
||||
## Authors and acknowledgment
|
||||
Show your appreciation to those who have contributed to the project.
|
||||
|
||||
## License
|
||||
For open source projects, say how it is licensed.
|
||||
|
||||
## Project status
|
||||
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user