commit | 0b7c6854f1b7b4b62c67a0048677653d0225938c | [log] [tgz] |
---|---|---|
author | Mohammad Asif Siddiqui <mohammad.asif.siddiqui1@huawei.com> | Tue Mar 13 13:53:11 2018 +0530 |
committer | GitHub <noreply@github.com> | Tue Mar 13 13:53:11 2018 +0530 |
tree | c14f90c1c098f0bf17a765630f085b48a3a68e23 | |
parent | 1b595b221e16e2500bbb9b6e1dfacf6669f69664 [diff] | |
parent | c52afc5598357319e34b3c50e3cf52e22ac036f2 [diff] |
Merge pull request #304 from little-cui/SCB-391 SCB-391 SC does not rotate log file
Apache ServiceComb (incubating) service-center allows services to register their instance information and to discover providers of a given service.
Project documentation is available on the ServiceComb website. You can also find some development guide here.
The easiest way to get Service Center is to use one of the pre-built release binaries which are available for Linux, Windows and Docker.
You can download our latest release from ServiceComb Website.When you get these release, you can execute the start script to run Service Center.
Windows(apache-incubator-servicecomb-service-center-XXX-windows-amd64.zip):
start-service-center.bat
Linux(apache-incubator-servicecomb-service-center-XXXX-linux-amd64.tar.gz):
./start-service-center.sh
Docker:
docker pull servicecomb/service-center docker run -d -p 30100:30100 servicecomb/service-center
Note: The Releases of Service-Center uses emebeded etcd, if you want to use the seperate instance of etcd then you can deploy the etcd seperately and configure the etcd ip over here.
vi conf/app.conf ## Edit this file # registry address # 1. if registry_plugin equals to 'embeded_etcd' # manager_name = "sc-0" # manager_addr = "http://127.0.0.1:2380" # manager_cluster = "sc-0=http://127.0.0.1:2380" # 2. if registry_plugin equals to 'etcd' # manager_cluster = "127.0.0.1:2379" manager_cluster = "127.0.0.1:2379"
By default the SC comes up on 127.0.0.1:30100, however you can change the configuration of these address over here.
vi conf/app.conf httpaddr = 127.0.0.1 httpport = 30100
Download the Code
git clone https://github.com/apache/incubator-servicecomb-service-center.git $GOPATH/src/github.com/apache/incubator-servicecomb-service-center cd $GOPATH/src/github.com/apache/incubator-servicecomb-service-center
Dependencies
We use gvt for dependency management, please follow below steps to download all the dependency.
go get github.com/FiloSottile/gvt gvt restore
If you face any issue in downloading the dependency because of insecure connection then you can use gvt restore -precaire
Build the Service-Center
go build -o service-center
First, you need to run a etcd(version: 3.x) as a database service and then modify the etcd IP and port in the Service Center configuration file (./etc/conf/app.conf : manager_cluster).
wget https://github.com/coreos/etcd/releases/download/v3.1.8/etcd-v3.1.8-linux-amd64.tar.gz tar -xvf etcd-v3.1.8-linux-amd64.tar.gz cd etcd-v3.1.8-linux-amd64 ./etcd cd $GOPATH/src/github.com/apache/incubator-servicecomb-service-center cp -r ./etc/conf . ./service-center
This will bring up Service Center listening on ip/port 127.0.0.1:30100 for service communication.If you want to change the listening ip/port, you can modify it in the Service Center configuration file (./conf/app.conf : httpaddr,httpport).
You can download our latest release from ServiceComb Website and then untar it and run start-frontend.sh/start-frontend.bat. This will bring up the Service-Center UI on http://127.0.0.1:30103.
Windows(apache-incubator-servicecomb-service-center-XXX-windows-amd64.zip):
start-frontend.bat
Linux(apache-incubator-servicecomb-service-center-XXXX-linux-amd64.tar.gz):
./start-frontend.sh
Note: By default frontend runs on 127.0.0.1, if you want to change this then you can change it in conf/app.conf
.
frontend_host_ip=127.0.0.1 frontend_host_port=30103
You can also change the the IP of Service-Center to which Frontend is connected over here app/apiList/apiList.js
You can follow the guide over here to run the Frontend from source.
Bugs: issues
See Contribution guide for details on submitting patches and the contribution workflow.
See reporting bugs for details about reporting any issues.