# flyway-demo
## 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.irootech.com/jialiang.xiao/flyway-demo.git
git branch -M main
git push -uf origin main
```
## Integrate with your tools
- [ ] [Set up project integrations](http://gitlab.irootech.com/jialiang.xiao/flyway-demo/-/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.
没有合适的资源?快使用搜索试试~ 我知道了~
分享微服务合并之多数据源整合(Dynamic Datasource)和Flyway对多数据源进行数据库脚本管理DEMO
共340个文件
xml:95个
class:23个
java:23个
需积分: 0 0 下载量 172 浏览量
2023-05-09
19:22:19
上传
评论
收藏 327KB ZIP 举报
温馨提示
【分享】微服务合并之多数据源整合(Dynamic Datasource)和Flyway对多数据源进行数据库脚本管理
资源推荐
资源详情
资源评论
收起资源包目录
分享微服务合并之多数据源整合(Dynamic Datasource)和Flyway对多数据源进行数据库脚本管理DEMO (340个子文件)
0302f50ba7f29cd7d7a992b2260a2f5ae732f2 653B
03d2bc31e1a738080a8949cbfef98cdd405c49 93B
03d4a14f24bde36f5adc66b5e4f64c560983ca 58B
061ff7ea4bc644ba8a13b59ba7994ce97dcec4 61B
065a95ad714bfe5f5d07fe471ff5d1562a4c2d 90B
0962bb517f65b37b5d39dca4468646247cf44f3d 0B
0ad5200421b85a3b6c8ca3b84d08dc9d09ce17 275B
0cf6c1a9b9498a09779e7b428c12f5a1669bc07c 227B
0eb8f1e14a4e43fbaa7300595174269003f277 68B
0ebcd5f0aa9c48de41e4bb6625db57a1eb872e 62B
0f96f741ffa75a724c7d3a168c745795d1bf75 49B
101ea8aac8af4635a593fc49bb7197438170c3 66B
18d2a1c52a7a7e7663b333a0422994938121ad 63B
18de260c091ed4de0cf9addfa3183638577e5b 64B
190dcb0cc24cb46f882ff21346643a59a2f4a0 179B
1a273f73b7a477b0745593641bd708a6182c7ad5 0B
1dbafa524cfbe0b741cb7d6f768e927d5d441d 44B
1e9114d1a4e85b066102ac7db5a07ef18ef59d 82B
1fa930a88a193a56455a8216974eaf5a7f954b 175B
20d8b78f104d76279b8882f6d5f77d00ee119e 161B
23f037c43662e1420cf11dd26b51ab16ad8711 55B
24ffebbbfdb4e2950b6098029e6cd08a937a9d 126B
250228af8a89e10cc904d08c6cbc56b3d8d2ef 74B
26239f80b80b74b33bec4c5ef77c35b5156c48 49B
27cfd49d4024c3e1e0d08ba56399221b4fb25d 1KB
29e53cd7a34f82c3a4c43918ff50960492f3f8 75B
2a053cc480d1f8668f9deb3e63e780cb731048 98B
2a134f5c1026ff7dd716bfcb375782af29d632 60B
2c9decd8611923ee5e1b3ea88c7227990cce76 49B
2d8192ce01a640c8867914568f5d4f9ef082ef 59B
2e4861334b3a8d96dda5c705deb132bafdc549e7 0B
30c84da0d5de6b840bd5aba86eba2798e2e15e41 0B
32271df5ea1c796e95ea36bf422cb94faa4dd9 571B
337e22a6aae594c3dc196d63bca6dffdad9d1090 0B
33db21561e21806ef851ddf1e23b1143f9b279 66B
34afc91505db5044cf505992490ebe554d6eb6f3 0B
37e2d54f73b72cdea9e0499651530463a027bd 53B
38ef5f630a96937e1b70b33da9b512798e0c88 125B
3a81730813d58e1b3ecad84d352cf302721f5d 506B
3ce025316ee14d3f19e71cba3f3a5b4b3c7970 371B
3f5c71f311cbbb279294b30be5a274066842c1 242B
4087054d8d8f723404d7f17a02a833cb664d79 925B
40d578aa592e87d3a3748ff52f7e6b8bedc64c 323B
41fef010225afd78c9bd15b9f59a32094dd8b5 221B
4224ae8a13bce52b9248e2bd90980775cfe7f7 74B
442292b8a7efeabbe4cc176709b833b1792140ec 0B
446fd92e2a7d8a2c1db8a3894c0b197f6035eecb 0B
44b3a49ae2e64051a983e491c5c3b656f1f752 49B
4a80c51818f736be4d1a4b6cc0da81195ecaac 80B
4c96d6bd5692e7bf636b95d6d9ab2f7b0db8a60e 0B
4d6952ff79e07c70607bffb47203ead313bdc7 712B
4d80cedc97356924c649beb7b10b0a8417acd1 95B
4dbac302fb5a3f2f3c98d593d8647aacc0dbac 74B
4e00ac9e58633dea4ddf496f88cb8f20b4d05e 483B
4ebd1940cc3744f608bec50d824ce964987072 174B
4fae87671b561056f25b9669a14c8beff8db5c 139B
505657bbe0ef2b528a9c5eae22422a10983fca 211B
51079a4c7dc1c7a47610c282bd7b17bb91f70a47 0B
53e1123b05e5f398f888d8075eb2d1cea33c0528 0B
56cc49416daaf6709063f2006691efe2ada870 94B
56cfff5454062c47f9028a7462a0f679d6fb0c 52B
5ddff13272f43ba53fb917c5b0f33b953b40ef 69B
634decbac007853f3fd17541a5665a43c966694a 0B
64979961a1130cf5b0411238438562e0965113 48B
6583aa50eb860d51f58d105b94f0aa493ac717 223B
687b29dd5a08cf7f583adaade60e226b545dd7e2 0B
68b807e483ccc56fad1b0c71e4ccbd4adde764 156B
6a7a810499955cb946d2c00acaf3ed570d28cf 234B
6b6503b5f1f4ba05f5ade73de05394df4a1b2e 164B
6b88551311dde6e7f1828fbd80b0979d6be6be 158B
6f57c9826e8b3171d77f6e3627c649284e4249 456B
703ccdfe27a8aec4b9c2e6f1f0f00d3ebe9b41 588B
70a38d94e0eed10074248e9e78ec237818198e 173B
720068adca036a4deda04b185770ed5ae2762a 1KB
73c76c6de0aff0271b35ac29af046d686f18ab 51B
746d9002a7bd16e9151ec48dcae3c660fc488f 179B
778283f4cd8604ec8f23ca9f900dd7426d7ae7 162B
792711d2032f0deea49f14f6aed27bfb8a4970 48B
79ee8211efe8c4bb76795ebc1312a7f71c8b1d 65B
7aa4e269b16cf7587167c1c99b44cdc53ff15b 1KB
7c3827e10d78230e8eceffef69c3305dc7dbbc8e 293B
7e1036ff4312362365ec1ec14efc9632a9ce3b 67B
7f0fcf69578e4ad9306d22eef57c114ec8ab01 179B
7fa9fde7ba60bae4a50cba14152a27d63caa1c 49B
80418d7e652a12ecd6d9e2b4c3a4a3703bc48c 72B
82bdf27dae18c55c6fdcd50565dabcd776857276 0B
847aca850e0ec7674321193d4127e0c18ae876 80B
882f418f2485d765d1795bd55e3c0f7cfe4155 457B
8bdda4622490dda2a9640264e8c93c3d7a87df 709B
8c30f1fc47c51354aab13efb043e02b935f235 45B
8d48d3948dace20f73bb565f52bedb5174c400 164B
8dea1fdd3042efa63752decd8ecc80419baa85 172B
8ea3ee28d849bafc6150c38d112a4ee9d4da28 97B
8ec9a00bfd09b3190ac6b22251dbb1aa95a0579d 0B
8f97aedd26f82c456b27f35d3a2f7309957d5f 64B
9255962a16752273da1ebe40a109ceb98e608b 72B
9472379cc338a503720bae33700b55b592157f 68B
983b6698f472623bd1b20ba4df5c5e39927d9b 220B
98a780b7139496ca01e6cbdc5f0475b46dda0e 449B
99ea21ed9f37e2a4d6cdad4581f4c9911e55d5 149B
共 340 条
- 1
- 2
- 3
- 4
资源评论
码农阿福
- 粉丝: 24
- 资源: 2
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
最新资源
- IMG_0694.GIF
- 基于图像的三维模型重建C++源代码+文档说明(高分课程设计)
- 基于聚焦法的工件立体测量方案,根据数据进行三维重建 使用HALCON处理图像,MATLAB拟合数据+源代码+数据集+效果图
- 锄战三国村 修改:货币使用不减 v1.10(2) 原创 (中文).apk
- 基于python实现的单目双目视觉三维重建+源代码+图像图片(高分课程设计)
- 基于C+++OPENCV的全景图像拼接源码(课程设计)
- 基于Python+OpenCV对多张图片进行全景图像拼接,消除鬼影,消除裂缝+源代码+文档说明+界面截图(高分课程设计)
- 基于C++实现的全景图像拼接源码(课程设计)
- 基于SIFT特征点提取和RASIC算法实现全景图像拼接python源码+文档说明+界面截图+详细注释(95分以上课程大作业)
- 基于matlab实现眼部判别的疲劳检测系统+源代码+全部数据+文档说明+详细注释+使用说明+截图(高分课程设计)
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功