commit | 4ad36176d38e76ec23ec03a4abc461ae3ec2d9a9 | [log] [tgz] |
---|---|---|
author | Alec.Zheng <aleczheng05@gmail.com> | Mon Oct 21 18:28:09 2019 +0800 |
committer | Willem Jiang <willem.jiang@gmail.com> | Mon Oct 21 18:28:09 2019 +0800 |
tree | 6018e979350d6022a65d7b416ec1e01655387029 | |
parent | b4dc01d3968b85023427e9074201b7552fab2229 [diff] |
[SCB-1538] add dependency licenses and better some docs (#45) * change Development Guide -> Development guide and add start server instruction to docs * add dependency licenses and change the build_binary.sh to add these licenses to binary package * add one of miss license * remove subcomponents license/notice infos from LICENSE/NOTICE file * remove the duplication apache2.0 license * revert build_binary.sh GO111MODULE modification * seperate go-chassis licenses * revert build_binary.sh GO111MODULE * rename LICENSE_go-chassis_go-chassis to LICENSE_Apache2.0 * change LICENSE AND NOTICE for go-chassis version upgrade * change the mispell seperate -> separate * add context.Background() for shutdown method * remove licenses/LICENSE and licenses/NOTICE from the binary package and change the path in LICENSE/NOTICE * change LICENSE_Apache2.0 path in licenses/LICENSE * change LICENSE file for apache license * change NOTICE format and files
A service for configuration management in distributed system.
key could indicate a configuration like “timeout”, then the value could be “3s” or indicates a file name “app.properties”, then the value could be content of app.properties
Each key could has labels. labels indicates a unique key. A key “log_level” with labels “env=production” may saves the value “INFO” for all application log level in production environment. A key “log_level” with labels “env=production, component=payment” may saves the value “DEBUG” for payment service in production environment.
it means all payment service print debug log, but for other service print info log.
so you can control your application runtime behaviors by setting different labels to a key.
it includes 5 components
TODO
git clone git@github.com:apache/servicecomb-kie.git cd servicecomb-kie/deployments/docker sudo docker-compose up
it will launch 3 components
To see how to build a local dev environment, check here
this will build your own service image and binary in local
cd build export VERSION=0.0.1 #optional, it is latest by default ./build_docker.sh
this will generate a “servicecomb-kie-0.0.1-linux-amd64.tar” in “release” folder, and a docker image “servicecomb/kie:0.0.1”
swagger/servicecomb-kie.yaml
follow here to generate it in local
Bugs: issues
See Contribution guide for details on submitting patches and the contribution workflow.
See reporting bugs for details about reporting any issues.