cookiecutter-django/{{cookiecutter.project_slug}}
Fabio C. Barrioneuvo da Luz 7740744885 sync migrations with django1.10
2016-09-29 01:01:01 -03:00
..
.ebextensions Add Experimental AWS Elastic Beanstalk support (#817) 2016-09-22 18:21:00 -07:00
.idea restore pycharm project configuration files 2016-05-01 20:28:34 -03:00
{{cookiecutter.project_slug}} sync migrations with django1.10 2016-09-29 01:01:01 -03:00
compose Update nginx.conf (#808) 2016-09-20 23:22:47 +02:00
config change 'admin' url, to stay the same as generated by django 1.10 2016-09-29 01:01:01 -03:00
docs simplify cookiecutter.json 2016-06-04 17:16:48 -07:00
requirements update django to 1.10.1 2016-09-29 01:00:55 -03:00
utility Change use_python2 [N] to use_python3 [Y] 2016-08-21 22:11:01 +02: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 NPM Logs (#796) 2016-09-16 15:28:22 +02:00
.pylintrc Change repo_name to project_slug for clarity. 2016-04-20 10:00:35 -07:00
.travis.yml Change use_python2 [N] to use_python3 [Y] 2016-08-21 22:11:01 +02:00
app.json postgresql versions are now selectable 2016-08-10 18:31:48 +03: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
dev.yml adds the ability to wait for the postgres container (#736) 2016-08-16 12:20:41 -07:00
docker-compose.yml Use latest redis docker image 2016-06-13 14:10:23 -07:00
ebsetenv.py Now includes message for missing .env file. Fixed #819 2016-09-26 09:28:35 -07:00
env.example Add Experimental AWS Elastic Beanstalk support (#817) 2016-09-22 18:21:00 -07:00
Gruntfile.js resolved merge conflicts 2016-05-22 20:18:08 +02:00
gulpfile.js fix: Gulpfile Issue #738 2016-08-25 16:07:17 +05:30
LICENSE Add GPLv3 licence support 2016-06-24 16:59:55 +02:00
manage.py ignore F401 error on manage.py 2016-09-29 00:58:26 -03:00
package.json fix: Gulpfile Issue #738 2016-08-25 16:07:17 +05:30
Procfile Use sentry for error reporting 2016-06-05 10:47:07 -07:00
pytest.ini Change repo_name to project_slug for clarity. 2016-04-20 10:00:35 -07:00
README.rst Fix elastic beanstalk checks 2016-09-28 16:42:02 -07:00
requirements.txt Change repo_name to project_slug for clarity. 2016-04-20 10:00:35 -07:00
runtime.txt Change use_python2 [N] to use_python3 [Y] 2016-08-21 22:11:01 +02:00
setup.cfg Change repo_name to project_slug for clarity. 2016-04-20 10:00:35 -07: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
{% 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.

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.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 {{cookiecutter.project_slug}}.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
^^^^^^^^^^^^
{% 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.

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

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.

.. _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 %}
{% endif %}
{% if cookiecutter.use_sentry_for_error_reporting == "y" %}

Sentry
^^^^^^

Sentry is an error logging aggregator service. You can sign up for a free account at  https://getsentry.com/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
^^^^^^

.. 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.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.use_elasticbeanstalk_experimental.lower() == 'y' %}

Elastic Beanstalk
~~~~~~~~~~~~~~~~~~

See detailed `cookiecutter-django Elastic Beanstalk documentation`_.

.. _`cookiecutter-django Docker documentation`: http://cookiecutter-django.readthedocs.io/en/latest/deployment-with-elastic-beanstalk.html

{% endif %}