|
a/README.markdown |
|
b/README.markdown |
|
... |
|
... |
| 56 |
(anvil)~/src$ git clone git://git.code.sf.net/p/allura/git.git forge
|
56 |
(anvil)~/src$ git clone git://git.code.sf.net/p/allura/git.git forge
|
| 57 |
|
57 |
|
| 58 |
Although the application setup.py files define a number of dependencies, the `requirements.txt` files are currently the authoritative source, so we'll use those with `pip` to make sure the correct versions are installed.
|
58 |
Although the application setup.py files define a number of dependencies, the `requirements.txt` files are currently the authoritative source, so we'll use those with `pip` to make sure the correct versions are installed.
|
| 59 |
|
59 |
|
| 60 |
(anvil)~/src$ cd forge
|
60 |
(anvil)~/src$ cd forge
|
| 61 |
(anvil)~/src/forge$ pip install -r requirements-dev.txt
|
61 |
(anvil)~/src/forge$ pip install -r requirements.txt
|
| 62 |
|
62 |
|
| 63 |
This will take a while. If you get an error from pip, it is typically a temporary download error. Just run the command again and it will quickly pass through the packages it already downloaded and then continue.
|
63 |
This will take a while. If you get an error from pip, it is typically a temporary download error. Just run the command again and it will quickly pass through the packages it already downloaded and then continue.
|
| 64 |
|
64 |
|
| 65 |
And now to setup each of the Forge applications for development. Because there are quite a few (at last count 15), we'll use a simple shell loop to set them up.
|
65 |
And now to setup each of the Forge applications for development. Because there are quite a few (at last count 15), we'll use a simple shell loop to set them up.
|
| 66 |
|
66 |
|