-
Notifications
You must be signed in to change notification settings - Fork 25
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Reorder and update installation instructions
- Loading branch information
Showing
1 changed file
with
66 additions
and
59 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -7,7 +7,7 @@ Connect is currently tested with ``Python 3.4`` and ``Django 1.7 & 1.8``. | |
Dependencies | ||
____________ | ||
|
||
Assuming you have the following installed: | ||
You will need to have the following installed: | ||
|
||
* Python 3 | ||
* pip | ||
|
@@ -41,7 +41,7 @@ running tests against the same database as production can sometimes pick up | |
edge case bugs early. | ||
|
||
If you're setting up a staging, production, or CI server, postgres is strongly | ||
recommended. Install it with `sudo apt-get install postgresql-9.4` or similar, | ||
recommended. Install it with ``sudo apt-get install postgresql-9.4`` or similar, | ||
and then set up a database for the connect app: | ||
|
||
.. code-block:: bash | ||
|
@@ -56,54 +56,43 @@ and then set up a database for the connect app: | |
=# \l # Check database access permissions | ||
=# \q # (or Ctrl-D) Exit from psql | ||
(You can substitute *connectdb* and *connectuser* as you wish, you will just need to reflect that in the `DATABASE_URL` you set below.) | ||
(You can substitute *connectdb* and *connectuser* as you wish, you will just need to reflect that in the ``DATABASE_URL`` you set below.) | ||
|
||
|
||
Environment variables | ||
_____________________ | ||
|
||
A fully configured connect instance requires the following environment variables: | ||
|
||
* `DATABASE_URL` -- db config syntax: "postgres://USER:PASSWORD@HOST:PORT/DB-NAME" | ||
* `SECRET_KEY` -- this should not be stored in your repository. | ||
* `ALLOWED_HOSTS` -- required when DEBUG=False, so for staging/ci/prod. | ||
* `DEFAULT_FROM_EMAIL` -- the from address for in-app emails | ||
* `MANDRILL_API_KEY` -- Mandrill is recommend for sending emails from the server | ||
* `DJANGO_MODE` -- outside dev, set this to "Production" or "Staging" | ||
* ``DATABASE_URL`` -- db config syntax: ``"postgres://USER:PASSWORD@HOST:PORT/DB-NAME"`` | ||
* ``SECRET_KEY`` -- this should not be stored in your repository. | ||
* ``ALLOWED_HOSTS`` -- required when ``DEBUG=False``, so for staging/ci/prod. | ||
* ``DEFAULT_FROM_EMAIL`` -- the from address for in-app emails | ||
* ``MANDRILL_API_KEY`` -- Mandrill is recommend for sending emails from the server | ||
* ``DJANGO_MODE`` -- outside dev, set this to "Production" or "Staging" | ||
|
||
All of these have working defaults in dev, but if you want to override any of | ||
**All of these have working defaults in dev**, but if you want to override any of | ||
them (eg to use postgres), you can set them like this: | ||
|
||
|
||
.. code-block:: bash | ||
export DATABASE_URL="postgres://connectuser:<password>@localhost:5432/connectdb" | ||
export SECRET_KEY="<a long string of random characters" | ||
export SECRET_KEY="a long string of random characters" | ||
export DEFAULT_FROM_EMAIL="[email protected]" | ||
#... etc | ||
**TIP:** a good place to set them is in the ``postactivate`` virtualenv hook, | ||
which will be somewhere like *~/.virtualenvs/connect/bin/postactivate*. For | ||
neatness, unset them in the ``predeactivate`` virtualenv hook too: | ||
.. tip:: | ||
A good place to set them is in the ``postactivate`` virtualenv hook, | ||
which will be somewhere like *~/.virtualenvs/connect/bin/postactivate*. For | ||
neatness, unset them in the ``predeactivate`` virtualenv hook too: | ||
|
||
.. code-block:: bash | ||
unset DATABASE_URL | ||
unset SECRET_KEY | ||
unset DEFAULT_FROM_EMAIL | ||
#... etc | ||
Additional configuration | ||
________________________ | ||
|
||
|
||
In ``settings.py``, you may also wish to override: | ||
|
||
* Admins | ||
* Timezone | ||
* Gravatar Settings | ||
.. code-block:: bash | ||
unset DATABASE_URL | ||
unset SECRET_KEY | ||
unset DEFAULT_FROM_EMAIL | ||
#... etc | ||
Initial database setup | ||
|
@@ -139,36 +128,13 @@ And you'll be able to open up the development site in your web browser at http:/ | |
#. Set up some additional data in your database. (See :doc:`configuration` for more information.) | ||
|
||
|
||
Edit scss files (style) | ||
_______________________ | ||
|
||
Connect is built with Sass_ and Compass_. | ||
|
||
If you need to install them, you will also need ``ruby`` but the installation process is beyond the scope of this project. | ||
|
||
Please refer to the Saas and Compass documentation. | ||
|
||
|
||
To compile locally your scss changes to the css file, use the command ``compass compile`` in the ``static/css`` folder of the app concerned by the changes. | ||
|
||
|
||
.. _Sass: http://sass-lang.com/ | ||
.. _Compass: http://compass-style.org/ | ||
|
||
|
||
.. rubric:: Example: Changing the highlighting color | ||
|
||
You can change the default pink highlight color by editing the ``$highlight`` | ||
variable at the top of ``static/css/sass/_color.scss`` | ||
|
||
|
||
Running Tests | ||
_____________ | ||
|
||
.. code-block:: bash | ||
$ ./manage.py test #to test the entire project. | ||
$ ./manage.py test <appname> #to test a specific django app | ||
$ python manage.py test #to test the entire project. | ||
$ python manage.py test connect/appname #to test a specific django app | ||
To run Connect's `Behave`_ tests, you will need to have PhantomJS_ installed. | ||
|
@@ -182,24 +148,65 @@ Run the BDD tests with: | |
|
||
.. code-block:: bash | ||
$ ./manage.py test bdd | ||
$ python manage.py test bdd | ||
To run an individual test feature, use | ||
|
||
.. code-block:: bash | ||
$ npm install phantomjs | ||
$ ./manage.py test bdd --behave_include featurename | ||
$ python manage.py test bdd --behave_include featurename | ||
Alternatively you can use any other `supported browser`_ (e.g. Chrome, Firefox) | ||
by installing it on your system and specifying it when you run your tests: | ||
|
||
.. code-block:: bash | ||
$ ./manage.py test bdd --behave_browser <browser> | ||
$ python manage.py test bdd --behave_browser <browser> | ||
.. _Behave: http://pythonhosted.org/behave/ | ||
.. _PhantomJS: http://phantomjs.org/ | ||
.. _`supported browser`: http://splinter.cobrateam.info/en/latest/index.html#drivers | ||
|
||
|
||
Editing SCSS files (style) | ||
__________________________ | ||
|
||
Connect is built with Sass_ and Compass_. | ||
|
||
To use them you will also need ``ruby`` - the installation process for this is beyond the scope of these instructions. Please refer to the Saas and Compass documentation for more information. | ||
|
||
To compile your SCSS into CSS, use: | ||
|
||
.. code-block:: bash | ||
compass compile connect/static/css # where final argument is a path to the css folder | ||
Or you can automatically update your changes with: | ||
|
||
.. code-block:: bash | ||
compass watch connect/static/css # where final argument is a path to the css folder | ||
.. _Sass: http://sass-lang.com/ | ||
.. _Compass: http://compass-style.org/ | ||
|
||
|
||
.. rubric:: Example: Changing the highlighting color | ||
|
||
You can change the default pink highlight color by editing the ``$highlight`` | ||
variable at the top of ``static/css/sass/_color.scss`` | ||
|
||
|
||
Additional configuration | ||
________________________ | ||
|
||
|
||
In ``settings.py``, you may also wish to override: | ||
|
||
* Admins | ||
* Timezone | ||
* Gravatar Settings |