From 71825fb4c26a1a1cc7091d62dba064064d2a5125 Mon Sep 17 00:00:00 2001 From: Paul McLanahan Date: Tue, 17 Mar 2015 16:32:04 -0400 Subject: [PATCH] Fix install docs. No longer need to install less manually. But do need `python-dev` package and to install l10n files for tests to pass. --- docs/install.rst | 17 +++++++---------- 1 file changed, 7 insertions(+), 10 deletions(-) diff --git a/docs/install.rst b/docs/install.rst index bc1da7b52d..6b42c89630 100644 --- a/docs/install.rst +++ b/docs/install.rst @@ -50,7 +50,7 @@ If you are on OSX and some of the compiled dependencies fails to compile, try ex If you are on Linux, you will need at least the following packages or their equivalent for your distro: - libmysqlclient-dev libxslt-dev + python-dev libmysqlclient-dev libxslt-dev Now configure the application to run locally by creating your local settings file:: @@ -62,19 +62,16 @@ Sync the database and all of the external data locally. This gets product-detail $ bin/sync_all -Lastly, you need to install `node` and the `less` package. Soon you won't need this for local development but currently it compiles the LESS CSS code on the server-side:: - - $ npm -g install less - -You don't have to use npm to install less; feel free to install it however you want. - -Add the path to the LESS compiler (found by using `which lessc`) to `bedrock/settings/local.py` with the following line:: - - LESS_BIN = '/path/to/lessc' +Lastly, you need to have `Node.js `_ installed. The node dependencies for running the site are in the repository, but if you'd like to run the JS test suite you'll need everything, which you can get by running `npm install` from the root directory of the project. Run the tests ------------- +.. Important:: + + We're working on fixing this, but for now you need the localization files for the tests to pass. + See the `Localization`_ section below for instructions on checking those out. + Now that we have everything installed, let's make sure all of our tests pass. This will be important during development so that you can easily know when you've broken something with a change. You should still have your virtualenv