cookiecutter-django/{{cookiecutter.repo_name}}
2016-01-08 13:21:45 +03:00
..
{{cookiecutter.repo_name}} Merge contributors change. 2016-01-06 21:37:23 -08:00
compose use REDIS_URL instead of DJANGO_CACHE_URL, fixes #379 2015-10-24 19:25:46 +02:00
config Merge contributors change. 2016-01-06 21:37:23 -08:00
docs Fix #313, which is removing dokku 2015-08-31 21:25:23 -07:00
requirements Bump Django to v1.9 2015-12-09 13:33:17 +01:00
tests fix issue #436 2015-12-11 09:05:49 -03:00
.coveragerc Use django_coverage_plugin to check template test coverage. 2015-11-11 21:07:16 -08:00
.editorconfig removed isort link 2015-10-21 13:19:08 -07:00
.gitattributes Add .gitattributes file. 2013-12-12 17:31:45 +05:30
.gitignore Add mailhog binary to gitignore 2015-11-18 11:16:44 +00:00
.pylintrc Add .pep8 and .pylintrc 2015-07-20 02:10:31 +01:00
.travis.yml Use python 3.5 on Travis 2015-11-18 15:07:08 +01:00
app.json Fix the template syntax error. 2015-10-04 05:51:09 -07:00
CONTRIBUTORS.txt Repo contributors should start with project author 2013-08-20 10:07:49 -04:00
dev.yml postgres 9.5 has arrived 2016-01-06 09:58:18 +01:00
docker-compose.yml postgres 9.5 has arrived 2016-01-06 09:58:18 +01:00
Dockerfile fixing typos (again) 2016-01-08 13:21:45 +03:00
Dockerfile-dev initial fixes for docker issue on windows 10 2016-01-06 20:04:36 +03:00
env.example DJANGO_SENTRY_DSN env variable if use_sentry 2015-12-16 17:53:28 +11:00
Gruntfile.js Fix merge conflict in README.rst 2015-11-18 11:16:25 +00:00
install_os_dependencies.sh Small improvements in install_python_dependencies.sh and install_os_dependencies.sh scripts 2015-08-30 22:56:19 -03:00
install_python_dependencies.sh Small improvements in install_python_dependencies.sh and install_os_dependencies.sh scripts 2015-08-30 22:56:19 -03:00
LICENSE Wrap all line-length to max 80 chars 2015-05-09 22:41:18 +05:30
manage.py Major refractor to move PYTHON_PATH to top-level repo dir 2015-04-26 11:35:46 +05:30
package.json Update package.json 2015-07-23 12:17:49 -07:00
Procfile Fix celery worker app name in Procfile 2015-12-15 15:29:00 -08:00
README.rst Fix merge conflict in README.rst 2015-11-18 11:16:25 +00:00
requirements.apt Added support for the Hitch integration testing framework. 2015-08-01 18:26:06 +08:00
requirements.txt update dependencies versions 2015-07-07 09:15:26 -03:00
runtime.txt Update runtime.txt 2015-12-11 17:42:30 -08:00
setup.cfg Move .pep8 to setup.cfg. 2015-09-26 00:47:44 -07:00

{{cookiecutter.project_name}}
==============================

{{cookiecutter.description}}


LICENSE: BSD

Settings
------------

Moved to settings_.

.. _settings: http://cookiecutter-django.readthedocs.org/en/latest/settings.html

Basic Commands
--------------

Setting Up Your Users
^^^^^^^^^^^^^^^^^^^^^

To create a **normal user account**, just go to Sign Up and fill out the form. Once you submit it, you'll see a "Verify Your E-mail Address" page. Go to your console to see a simulated email verification message. Copy the link into your browser. Now the user's email should be verified and ready to go.

To create an **superuser account**, use this command::

    $ python manage.py createsuperuser

For convenience, you can keep your normal user logged in on Chrome and your superuser logged in on Firefox (or similar), so that you can see how the site behaves for both kinds of users.

Test coverage
^^^^^^^^^^^^^

To run the tests, check your test coverage, and generate an HTML coverage report::

    $ coverage run manage.py test
    $ coverage html
    $ open htmlcov/index.html

Live reloading and Sass CSS compilation
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Moved to `Live reloading and SASS compilation`_.

.. _`Live reloading and SASS compilation`: http://cookiecutter-django.readthedocs.org/en/latest/live-reloading-and-sass-compilation.html

{% if cookiecutter.use_celery == "y" %}

Celery
^^^^^^

This app comes with Celery.

To run a celery worker:

.. code-block:: bash

    cd {{cookiecutter.repo_name}}
    celery -A {{cookiecutter.repo_name}}.taskapp worker -l info

Please note: For Celerys import magic to work, it is important *where* the celery commands are run. If you are in the same folder with *manage.py*, you should be right.

{% endif %}

{% if cookiecutter.use_mailhog == "y" %}

Email Server
^^^^^^^^^^^^

In development, it is often nice to be able to see emails that are being sent from your application. If you choose to use `MailHog`_ when generating the project a local SMTP server with a web interface will be available.

.. _mailhog: https://github.com/mailhog/MailHog

To start the service, make sure you have nodejs installed, and then type the following::

    $ npm install
    $ grunt serve

(After the first run you only need to type ``grunt serve``) This will start an email server that listens on ``127.0.0.1:1025`` in addition to starting your Django project and a watch task for live reload.

To view messages that are sent by your application, open your browser and go to ``http://127.0.0.1:8025``

The email server will exit when you exit the Grunt task on the CLI with Ctrl+C.

{% endif %}

{% if cookiecutter.use_sentry == "y" %}

Sentry
^^^^^^

Sentry is an error logging aggregator service. You can sign up for a free account at http://getsentry.com or download and host it yourself.
The system is setup with reasonable defaults, including 404 logging and integration with the WSGI application.

You must set the DSN url in production.

{% endif %}

It's time to write the code!!!


Running end to end integration tests
------------------------------------

N.B. The integration tests will not run on Windows.

To install the test runner::

  $ pip install hitch

To run the tests, enter the {{cookiecutter.repo_name}}/tests directory and run the following commands::

  $ hitch init

Then run the stub test::

  $ hitch test stub.test

This will download and compile python, postgres and redis and install all python requirements so the first time it runs it may take a while.

Subsequent test runs will be much quicker.

The testing framework runs Django, Celery (if enabled), Postgres, HitchSMTP (a mock SMTP server), Firefox/Selenium and Redis.


Deployment
----------

We providing tools and instructions for deploying using Docker and Heroku.

Heroku
^^^^^^

.. image:: https://www.herokucdn.com/deploy/button.png
    :target: https://heroku.com/deploy

See detailed `cookiecutter-django Heroku documentation`_.

.. _`cookiecutter-django Heroku documentation`: http://cookiecutter-django.readthedocs.org/en/latest/deployment-on-heroku.html

Docker
^^^^^^

See detailed `cookiecutter-django Docker documentation`_.

.. _`cookiecutter-django Docker documentation`: http://cookiecutter-django.readthedocs.org/en/latest/deployment-with-docker.html