bfacfc8ff7
Add missing developer docs for unit test, etcd db and writing developer guide. Fix errors occurred when building developer docs with Sphinx : # tox -e docs Fix some other nits. Change-Id: I8580af70630edd0c214645ce4b6bbcd308925aa1 Closes-Bug: #1653198 Signed-off-by: Andy Yan <yanchao3@lenovo.com>
1.1 KiB
Copyright 2016 Intel Corporation All Rights Reserved.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
Deploy Valence Project
This document describes how to update the code base of Valence after installation. Whenever valence code has been updated, either through git or modifying it locally, it needs to be deployed to standard python path. The below steps describes them.
Execute the below bash commands in the valence root directory (where the setup.py file exists)
$ python setup.py install $ sudo service valence restart