mirror of
https://github.com/cookiecutter/cookiecutter-django.git
synced 2024-11-22 17:47:08 +03:00
158 lines
4.6 KiB
ReStructuredText
158 lines
4.6 KiB
ReStructuredText
{{cookiecutter.project_name}}
|
|
==============================
|
|
|
|
{{cookiecutter.description}}
|
|
|
|
.. image:: https://img.shields.io/badge/built%20with-Cookiecutter%20Django-ff69b4.svg
|
|
:target: https://github.com/pydanny/cookiecutter-django/
|
|
:alt: Built with Cookiecutter Django
|
|
|
|
{% if cookiecutter.open_source_license != "Not open source" %}
|
|
LICENSE: {{cookiecutter.open_source_license}}
|
|
{% endif %}
|
|
|
|
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
|
|
|
|
Running tests with py.test
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
::
|
|
|
|
$ py.test
|
|
|
|
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 Celery's 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 provide 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
|