# smallrig-data-board
数据看板
## Getting started
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)!
## 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:
```
cd existing_repo
git remote add origin http://gitlab.smallrig.net/root/smallrig-data-board.git
git branch -M master
git push -uf origin master
```
## Integrate with your tools
- [ ] [Set up project integrations](http://gitlab.smallrig.net/root/smallrig-data-board/-/settings/integrations)
## 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)
## Test and Deploy
Use the built-in continuous integration in GitLab.
- [ ] [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)
***
# 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.
## 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.
## 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.
## 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.
## 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.
没有合适的资源?快使用搜索试试~ 我知道了~
分库分表数据看板项目实战
共4810个文件
class:314个
java:255个
xml:58个
需积分: 2 0 下载量 103 浏览量
2022-10-24
14:06:00
上传
评论
收藏 106.05MB RAR 举报
温馨提示
分库分表数据看板项目实战
资源详情
资源评论
资源推荐
收起资源包目录
分库分表数据看板项目实战 (4810个子文件)
0008439e2b7cf30814d280304dfcfb9830342d 47B
001dff63ebce9dade41f47d0db486448fc19c5 352B
0030a7d39d7700c627e7599c03736aa653b8a3 51B
0031899c30aee71c2d559e597b953d2a146c08 547B
00408b65ebf9c0f4bf2c56c0766b2595a96266 50B
0041bae9a0636ed05ef07662001956d9508ee8 217B
0053b07bd96c955021744dc3ea23691be2256f 46B
0068abab09fc033c9af99a23b14564e47a2876 2KB
006940a17eb61fca654a80b4f1c5a4cc3d44dd 47B
00749ce6d5dd3ab5147205cb3e0f10393b91ca 632B
0082a55791c16a27adf02402031a934b99b7b5 402B
009a41c12cf9a12a9b10373c664830702790f7 45B
00a410caf3bcdce4990ece3595e1e875d5cfe3 1KB
00a618d2652ac45b4a8b1dffd375b81d8a8f4d 572B
00bbaacdcd2dba80dbcb624158070f4c9c8d5d 528B
00d9b6fb3c5c086d583d0fa98e60b03fe56b6d 548B
00dd71375f5b7ac48664b734a68714e555cb79 114B
00de53f6cd951930e52a936c0dbe5159e2db0f 2KB
00f390ce1832ce2db6afc6090fe70c070905e6 722B
00f3f42b51892693f61a4d5ddd63b8599f1c2b 428B
00ffa821d50e59767e9ae3f50135b030261405 593B
010c28a5b2e090a5ce04f8ecd3db7ae0eb954e 719B
010f47be4e78404349bbc4757a639e9f445442 793B
011b140789cb1582a772308e95cc6cd00c0ec4 3KB
011d715e24c3d9c0bf52c3dacf469fb2223ed3 548B
011f3de7b0cf3fb4398bde6e5d14fd48480e7a 46B
01263d42202322c68197817545780cfb0f6488 45B
012dc6b81ad4682c55dc26d47a81f223d249b1 914B
012de47c17ee45dc437ca3defa6f6604edd8d5 167B
01328ea30f18114e218e2d1ac168411872e7d9 913B
0150a3bf02a22a3414c952d4cda8c6435f27ee 46B
0156244c0244cf506e637a556c091d330b8c13 168B
015cdaedf2b544a127267db57d458b263e4771 47B
01608b819ffd70cec274b91841363f83662582 130B
01612549b581f42ffb472cc2bf6bb79b17eb24 238B
016e57433c5eef9b06b92cee89878f5a7da348 46B
01738c1d53e62ba00c4d8757adfcd123f9c4c7 578B
017b739041901b24c9f929a18b6fa2f8ac56c4 562B
0188bc8374d328c495c95858606299060a1474 162B
018e250b0272f44f0ffc2add7e8eb71ffa968a 793B
019158236d11f3f0059101d412cbfe4653eed4 46B
019db1a301746a086caa735408be40ef6be58c 115B
01a636b11f597cdb3c73b0ad1dc6a34652300c 2KB
01a691b2559ac91aca97f2a0d35d9eab7da4eb 89B
01d31229ca31a8e19763d9cf1d899809bfb247 2KB
01d6bed2a01234ef391eaabc36e69411cc16e8 79B
01fc88ff16885c2829f2a0add9f3ce0b2f138c 258B
020b120ac06d40ecba00004bf3bf2e926646af 506B
02316cb387d4aa81273f258bad76d0a7b33762 1KB
02383796de65c5355d292ecf6044e44aa15291 46B
023f1a4e19a1d4c83062552b3e23d5c07c90d2 3KB
024554d26220fed715e0d8d79dff0fcc699b07 424B
024fa8c0771717f8a4a17bcf5bf57d98deb3f3 577B
0261509a1b71947a9fff95a83f4358b3c9d7fb 45B
0263e4e99203c1bc76d94952910c6277d83500 363B
0267edce198be951ccda6400bb4db43ba90319 548B
028f78f33bb09c009e9058fd73cace6c3ddcaa 79B
029f4fe7e78aa297cb590176574e4cdabb8171 503B
02a2fed50f940a0d530625e3c8b214ba24c50e 841B
02c09533f6c5ffe4827b395fc8d4d9201d8c5d 45B
02d3ee5233d7a0edce88fec0f54af5cd9dd455 126B
02dd295fb49c1c8eadb045eb3419a3e37318f3 547B
02e86d19e81d2ea89622c5ad36d9aad0227108 171B
02f55426fc44cffb2b59f03125916da00067d5 698B
030955ff1ab6759a5c8e3bc1f251afcdbd785c 91B
030e2ace55a3a1abc1c4dc71847875e8000402 46B
0314d83203dec33e4319cc6b1f7d3676d3ae03 45B
031856bd8f407c6f15e3bfe9d29465246eb799 752B
03245d60f343371c19ccdbc166234e67f27a67 286B
03293b690b151ba7b0e807973c248d70c65485 47B
0329b58676abfa8175b5869794f64f4ec071f8 354B
0329de52090e1e4d6e5c818487d4965d3a8a6e 416B
032f58e1b384675903780dbaa1328f827ab961 130B
034238396f3b14a5c31be6868ffdf0df780e29 203B
036b6c995061dcd91a0708afb18a87c9c67558 548B
0372c8859421e567b0ccab3ad922148b6e3b71 580B
0373788f777ef98c63500afd529f4470eeca43 453B
037de7a484cfcc5516ccf88603d1d003507bdc 299B
0386850c240448cb652a4662ecda884b6bfcc0 1KB
038a690ad0310df7e1f6fe9e7e594043a7390a 47B
039d9c2f870f2d6dcf2abba0cbb3613558a553 264B
03a2cbf767c0baf829064750d960e0fa90ad4f 655B
03a63d33dc3a720271667cb78b1c8e36a25414 2KB
03c1562296225e1427c1a3c5d86af0a53d70b4 46B
03d86c88fd29a33c3e662705b315ca1cd67584 248B
03d9d131166c7f53374b5df94b015d20abb7a6 47B
03f3d86b6d6b980cd8ceb9c8c22b53cb7665a6 444B
04267d5537fc2dc17756212539a3e1cc6223be 47B
0441548e14e6e4cbfd457fa951b946124b100a 47B
045ac2d7508b9264d46412474d96320d82967c 581B
045dda5872d6c755c05fcf2d89bc67d4b504eb 268B
04718b8a3c077d99b0d80cb306ffada8866e40 255B
049078d86fc0a5711d764297af250ba90b23cc 2KB
049c3955cc8abfc0b8ad8cedb26469b166684e 547B
04a6ae814c6340019aabee0c2f293e5277d52e 46B
04a89d058e71ef4ee2c80bf2f76530b6d2aa6a 47B
04b8dba5b91df3ca34cf89ef41feb784f03b25 47B
04c523256630023e88ce5f65661bca8d177ce2 593B
04e90905ef5bcb426d5231473ca20421f44187 352B
053748250e8f0189511e664f3b7685d0a56632 246B
共 4810 条
- 1
- 2
- 3
- 4
- 5
- 6
- 49
微云村
- 粉丝: 4
- 资源: 15
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
最新资源
- 筷手引流工具.apk
- 论文(最终)_20240430235101.pdf
- 基于python编写的Keras深度学习框架开发,利用卷积神经网络CNN,快速识别图片并进行分类
- 最全空间计量实证方法(空间杜宾模型和检验以及结果解释文档).txt
- 5uonly.apk
- 蓝桥杯Python组的历年真题
- 2023-04-06-项目笔记 - 第一百十九阶段 - 4.4.2.117全局变量的作用域-117 -2024.04.30
- 2023-04-06-项目笔记 - 第一百十九阶段 - 4.4.2.117全局变量的作用域-117 -2024.04.30
- 前端开发技术实验报告:内含4四实验&实验报告
- Highlight Plus v20.0.1
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功
评论0