Skip to content

Commit bdf5dae

Browse files
[docs] remove not working dev setup
also add the command to clone the repository and use the pip-install `--editable` option in it's long form so it's immediately clear what it does. Change-Id: I00403f967c06af6d8c718ed1245aaa01f1218add Signed-off-by: Sven Kieske <[email protected]>
1 parent 428f371 commit bdf5dae

File tree

1 file changed

+5
-13
lines changed

1 file changed

+5
-13
lines changed

doc/source/contributor/running-in-development.rst

Lines changed: 5 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -7,23 +7,15 @@ Running Kolla Build in development
77
The recommended way to run in development
88
-----------------------------------------
99

10-
The preferred way to run kolla-build for development is using ``tox``.
11-
Run the following from inside the repository:
10+
To clone the repository and install the package
11+
in development mode, run the following commands:
1212

13-
.. code-block:: console
14-
15-
tox -e venv -- kolla-build ...
16-
17-
The alternative way to run in development
18-
-----------------------------------------
19-
20-
Sometimes, developers prefer to manage their venvs themselves. This is also
21-
possible. Remember to install in editable mode (``-e``). Run the following from
22-
inside the repository:
2313

2414
.. code-block:: console
2515
16+
git clone https://opendev.org/openstack/kolla.git
17+
cd kolla
2618
python3 -m venv ~/path/to/venv
2719
source ~/path/to/venv/bin/activate
28-
python3 -m pip install -e .
20+
python3 -m pip install --editable .
2921
kolla-build ...

0 commit comments

Comments
 (0)