WingsBoot=BKB + BootsOfTravel + SpringBoot. if you've liked Dota, you know.
We advocate defensive programming, May Thefalse
Be With You !English 🇺🇸 | 中文 🇨🇳
- Philosophy and Conventions, Non-Intrusion Enhancement 🌱 Apache2
- Main business language, OpenJDK long-time running ☕️ GPLv2+CE
- Assisted language, as a better Java Apache2
- The main type-safe SqlMapping 🏅 Apache2
- Main business database, recommend 8.0.31 💡 GPLv2
- Standalone database for offline and disconnected operations MPL2 or EPL1
- Distributed caching, messaging, streaming, etc. Apache2
- more engineering and compact miscroservice solution Apache2
- Database RW splitting, data sharding and elastic scaling Apache2
- Official Doc - https://wings.fessional.pro
- NotBad Code Review - https://java-code-review.moilioncircle.com
- Doc GitHub - https://github.com/fessionalpro/wings-doc
- Mirror Site - https://gitee.com/trydofor
## (1) get source code
git clone --depth 1 https://github.com/\
trydofor/professional-wings.git
## (2) install dependency using java8
# asdf shell java temurin-8.0.412+8
git submodule update --remote --init
(cd observe/meepo && mvn package install)
(cd observe/mirana && mvn package install)
## (3) install wings using java-21
# asdf shell java temurin-21.0.3+9.0.LTS
mvn package install
## (4) report issue
java -jar silencer-*-SNAPSHOT.jar
All SNAPSHOT
s are in development, rollup
iteration, gitflow
conventions.
All feature
branches are named after the dota2
hero,
about 1 push/week, 1 iteration/month, keep the last 2 branches.
Codes and docs use github
as the main site and gitee
as the mirror,
basically synchronized push.
- issues - task like action, such as bugs and features
- discussions - doc, tech topics, no political, religious discussions.
- PR and Review - PR will be reviewed and merged as the gitflow process
We will keep contributor and footprint as much as possible, such as @author comments, code comments, commit information, etc.
WingsBoot and its submodule projects are licensed under Apache2. Please note that,
- The projects are voluntary contributions based on existing technologies, resources and team practices, without any express or implied warranties or conditions.
- The developers of the projects have made efforts to ensure the quality and functionality of the code, but do not guarantee that the projects are completely free of defects or bugs.
- When using the projects, you must make your own evaluation of their suitability and assume all risks associated with their use.
- Under no circumstances will the developers of the projects be liable for any loss, damages, or other liabilities arising from the use of the projects.