cookiecutter-django/{{cookiecutter.project_slug}}
2019-08-25 14:08:28 +02:00
..
.envs Use GCP acronym for Google Cloud Platform 2019-05-27 17:39:45 -03:00
.idea Rename py.test to pytest in PyCharm config 2019-06-15 11:48:50 +01:00
{{cookiecutter.project_slug}} Merge pull request #2160 from 2O4/message_on_user_update 2019-07-17 21:11:43 +01:00
compose Remove all end-of-line carriage returns and not just the first occurrence 2019-06-19 09:46:10 +02:00
config Remove AWS_PRELOAD_METADATA 2019-08-25 14:08:28 +02:00
docs Fix typo 2019-06-15 06:37:58 +10:00
locale Move to the python:alpine docker image (#1482) 2018-02-22 10:01:05 -05:00
requirements Update pytest from 5.1.0 to 5.1.1 2019-08-21 13:00:30 +02:00
utility Add OS requirements for Ubuntu Bionic 18.04 2019-03-20 12:54:58 +00:00
.coveragerc Change repo_name to project_slug for clarity. 2016-04-20 10:00:35 -07:00
.dockerignore Change repo_name to project_slug for clarity. 2016-04-20 10:00:35 -07:00
.editorconfig Update nginx.conf (#808) 2016-09-20 23:22:47 +02:00
.gitattributes Change repo_name to project_slug for clarity. 2016-04-20 10:00:35 -07:00
.gitignore Remove dead link in .gitignore 2019-03-20 12:16:43 +00:00
.pylintrc add plugins to req file; remove pylint-common 2019-03-23 00:01:23 -04:00
.travis.yml Add Postgres service to Travis config 2019-06-06 17:23:37 +01:00
CONTRIBUTORS.txt Add spaces around templated author name 2016-08-24 15:48:03 -07:00
COPYING Add GPLv3 licence support 2016-06-24 16:59:55 +02:00
gulpfile.js Add a node image to run Gulp when selecting it with Docker (#1687) 2019-03-25 12:10:55 +00:00
LICENSE Add GPLv3 licence support 2016-06-24 16:59:55 +02:00
local.yml Update Redis version to 5.0 2019-05-18 13:54:25 +01:00
manage.py First pass at running black across the project (#1602) 2018-04-08 17:03:29 -05:00
merge_production_dotenvs_in_dotenv.py Replace Caddy with Traefik (#1714) 2019-03-19 09:32:45 +00:00
package.json Add a node image to run Gulp when selecting it with Docker (#1687) 2019-03-25 12:10:55 +00:00
Procfile Refactor Celery integration according to current best practices 2019-04-02 15:40:32 +01:00
production.yml Update Redis version to 5.0 2019-05-18 13:54:25 +01:00
pytest.ini Always use test settings in pytest 2019-07-09 08:54:31 +08:00
README.rst Refactor Celery integration according to current best practices (#2016) 2019-05-17 21:38:00 +01:00
requirements.txt Simplify post hook 2018-03-04 14:43:54 +03:00
runtime.txt Update to latest bug fix for Python 3.6 to fix Heroku warning when deploying 2019-03-11 22:02:11 +00:00
setup.cfg Add mypy to the local dependencies 2018-07-02 10:22:48 +03:00

{{cookiecutter.project_name}}
{{ '=' * cookiecutter.project_name|length }}

{{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
.. image:: https://img.shields.io/badge/code%20style-black-000000.svg
     :target: https://github.com/ambv/black
     :alt: Black code style
{% if cookiecutter.open_source_license != "Not open source" %}

:License: {{cookiecutter.open_source_license}}
{% endif %}

Settings
--------

Moved to settings_.

.. _settings: http://cookiecutter-django.readthedocs.io/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.

Type checks
^^^^^^^^^^^

Running type checks with mypy:

::

  $ mypy {{cookiecutter.project_slug}}

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

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

    $ coverage run -m pytest
    $ coverage html
    $ open htmlcov/index.html

Running tests with py.test
~~~~~~~~~~~~~~~~~~~~~~~~~~

::

  $ pytest

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

Moved to `Live reloading and SASS compilation`_.

.. _`Live reloading and SASS compilation`: http://cookiecutter-django.readthedocs.io/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.project_slug}}
    celery -A config.celery_app 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
^^^^^^^^^^^^
{% if cookiecutter.use_docker == 'y' %}
In development, it is often nice to be able to see emails that are being sent from your application. For that reason local SMTP server `MailHog`_ with a web interface is available as docker container.

Container mailhog will start automatically when you will run all docker containers.
Please check `cookiecutter-django Docker documentation`_ for more details how to start all containers.

With MailHog running, to view messages that are sent by your application, open your browser and go to ``http://127.0.0.1:8025``
{% else %}
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.

#. `Download the latest MailHog release`_ for your OS.

#. Rename the build to ``MailHog``.

#. Copy the file to the project root.

#. Make it executable: ::

    $ chmod +x MailHog

#. Spin up another terminal window and start it there: ::

    ./MailHog

#. Check out `<http://127.0.0.1:8025/>`_ to see how it goes.

Now you have your own mail server running locally, ready to receive whatever you send it.

.. _`Download the latest MailHog release`: https://github.com/mailhog/MailHog/releases
{% endif %}
.. _mailhog: https://github.com/mailhog/MailHog
{% endif %}
{% if cookiecutter.use_sentry == "y" %}

Sentry
^^^^^^

Sentry is an error logging aggregator service. You can sign up for a free account at  https://sentry.io/signup/?code=cookiecutter  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 %}

Deployment
----------

The following details how to deploy this application.
{% if cookiecutter.use_heroku.lower() == "y" %}

Heroku
^^^^^^

See detailed `cookiecutter-django Heroku documentation`_.

.. _`cookiecutter-django Heroku documentation`: http://cookiecutter-django.readthedocs.io/en/latest/deployment-on-heroku.html
{% endif %}
{% if cookiecutter.use_docker.lower() == "y" %}

Docker
^^^^^^

See detailed `cookiecutter-django Docker documentation`_.

.. _`cookiecutter-django Docker documentation`: http://cookiecutter-django.readthedocs.io/en/latest/deployment-with-docker.html
{% endif %}

{% if cookiecutter.custom_bootstrap_compilation == "y" %}
Custom Bootstrap Compilation
^^^^^^

The generated CSS is set up with automatic Bootstrap recompilation with variables of your choice.
Bootstrap v4 is installed using npm and customised by tweaking your variables in ``static/sass/custom_bootstrap_vars``.

You can find a list of available variables `in the bootstrap source`_, or get explanations on them in the `Bootstrap docs`_.

{% if cookiecutter.js_task_runner == 'Gulp' %}
Bootstrap's javascript as well as its dependencies is concatenated into a single file: ``static/js/vendors.js``.
{% endif %}

.. _in the bootstrap source: https://github.com/twbs/bootstrap/blob/v4-dev/scss/_variables.scss
.. _Bootstrap docs: https://getbootstrap.com/docs/4.1/getting-started/theming/

{% endif %}