|author||GuoYL <53255576+GuoYL123@users.noreply.github.com>||Wed Sep 02 17:58:13 2020 +0800|
|committer||GitHub <firstname.lastname@example.org>||Wed Sep 02 17:58:13 2020 +0800|
refactory db init func (#160)
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.
kie is a highly flexible config server. Nowadays, an operation team is facing different “x-centralized” system. For example a classic application-centralized system. A operator wants to change config based on application name and version, then the label could be “app,version” for locating a app‘s configurations. Meanwhile some teams manage app in a data center, each application instance will be deployed in a VM machine. then label could be “farm,role,server,component” to locate a app’s configurations. kie fit different senario for configuration management which benifit from label design.
It includes 1 components
git clone email@example.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”
or follow here to generate it in local
See Contribution guide for details on submitting patches and the contribution workflow.
See reporting bugs for details about reporting any issues.