mirror of
https://github.com/cookiecutter/cookiecutter-django.git
synced 2024-11-25 19:14:03 +03:00
291 lines
11 KiB
ReStructuredText
291 lines
11 KiB
ReStructuredText
Cookiecutter Django
|
|
=======================
|
|
|
|
.. image:: https://pyup.io/repos/github/pydanny/cookiecutter-django/shield.svg
|
|
:target: https://pyup.io/repos/github/pydanny/cookiecutter-django/
|
|
:alt: Updates
|
|
|
|
.. image:: https://travis-ci.org/pydanny/cookiecutter-django.svg?branch=master
|
|
:target: https://travis-ci.org/pydanny/cookiecutter-django?branch=master
|
|
:alt: Build Status
|
|
|
|
.. image:: https://badges.gitter.im/Join Chat.svg
|
|
:target: https://gitter.im/pydanny/cookiecutter-django?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge
|
|
|
|
Powered by Cookiecutter_, Cookiecutter Django is a framework for jumpstarting production-ready Django projects quickly.
|
|
|
|
* Documentation: https://cookiecutter-django.readthedocs.io/en/latest/
|
|
* See Troubleshooting_ for common errors and obstacles
|
|
* If you have problems with Cookiecutter Django, please open issues_ before sending emails to the maintainers. You will get a much, MUCH faster response.
|
|
|
|
.. _cookiecutter: https://github.com/audreyr/cookiecutter
|
|
|
|
.. _Troubleshooting: https://cookiecutter-django.readthedocs.io/en/latest/troubleshooting.html
|
|
|
|
.. _528: https://github.com/pydanny/cookiecutter-django/issues/528#issuecomment-212650373
|
|
.. _issues: https://github.com/pydanny/cookiecutter-django/issues/new
|
|
|
|
Features
|
|
---------
|
|
|
|
* For Django 1.10
|
|
* Renders Django projects with 100% starting test coverage
|
|
* Twitter Bootstrap_ v4.0.0 - `alpha 4`_ (`maintained Foundation fork`_ also available)
|
|
* 12-Factor_ based settings via django-environ_
|
|
* Secure by default. We believe in SSL.
|
|
* Optimized development and production settings
|
|
* Registration via django-allauth_
|
|
* Comes with custom user model ready to go
|
|
* Grunt build for compass and livereload
|
|
* Send emails via Anymail_ (using Mailgun_ by default, but switchable)
|
|
* Media storage using Amazon S3
|
|
* Docker support using docker-compose_ for development and production
|
|
* Procfile_ for deploying to Heroku
|
|
* Instructions for deploying to PythonAnywhere_
|
|
* Works with Python 2.7.x or 3.5.x
|
|
* Run tests with unittest or py.test
|
|
* Customizable PostgreSQL version
|
|
* Experimental support for Amazon Elastic Beanstalk
|
|
|
|
.. _`maintained Foundation fork`: https://github.com/Parbhat/cookiecutter-django-foundation
|
|
|
|
|
|
Optional Integrations
|
|
---------------------
|
|
|
|
*These features can be enabled during initial project setup.*
|
|
|
|
* Serve static files from Amazon S3 or Whitenoise_
|
|
* Configuration for Celery_
|
|
* Integration with MailHog_ for local email testing
|
|
* Integration with Sentry_ for error logging
|
|
* Integration with Opbeat_ for performance monitoring
|
|
|
|
.. _`alpha 4`: http://blog.getbootstrap.com/2016/09/05/bootstrap-4-alpha-4/
|
|
.. _Bootstrap: https://github.com/twbs/bootstrap
|
|
.. _django-environ: https://github.com/joke2k/django-environ
|
|
.. _12-Factor: http://12factor.net/
|
|
.. _django-allauth: https://github.com/pennersr/django-allauth
|
|
.. _django-avatar: https://github.com/grantmcconnaughey/django-avatar
|
|
.. _Procfile: https://devcenter.heroku.com/articles/procfile
|
|
.. _Mailgun: http://www.mailgun.com/
|
|
.. _Whitenoise: https://whitenoise.readthedocs.io/
|
|
.. _Celery: http://www.celeryproject.org/
|
|
.. _Anymail: https://github.com/anymail/django-anymail
|
|
.. _MailHog: https://github.com/mailhog/MailHog
|
|
.. _Sentry: https://sentry.io/welcome/
|
|
.. _docker-compose: https://github.com/docker/compose
|
|
.. _Opbeat: https://opbeat.com/
|
|
.. _PythonAnywhere: https://www.pythonanywhere.com/
|
|
|
|
|
|
Constraints
|
|
-----------
|
|
|
|
* Only maintained 3rd party libraries are used.
|
|
* Uses PostgreSQL everywhere (9.2+)
|
|
* Environment variables for configuration (This won't work with Apache/mod_wsgi).
|
|
|
|
|
|
Usage
|
|
------
|
|
|
|
Let's pretend you want to create a Django project called "redditclone". Rather than using `startproject`
|
|
and then editing the results to include your name, email, and various configuration issues that always get forgotten until the worst possible moment, get cookiecutter_ to do all the work.
|
|
|
|
First, get Cookiecutter. Trust me, it's awesome::
|
|
|
|
$ pip install "cookiecutter>=1.4.0"
|
|
|
|
Now run it against this repo::
|
|
|
|
$ cookiecutter https://github.com/pydanny/cookiecutter-django
|
|
|
|
You'll be prompted for some values. Provide them, then a Django project will be created for you.
|
|
|
|
**Warning**: After this point, change 'Daniel Greenfeld', 'pydanny', etc to your own information.
|
|
|
|
Answer the prompts with your own desired options_. For example::
|
|
|
|
Cloning into 'cookiecutter-django'...
|
|
remote: Counting objects: 550, done.
|
|
remote: Compressing objects: 100% (310/310), done.
|
|
remote: Total 550 (delta 283), reused 479 (delta 222)
|
|
Receiving objects: 100% (550/550), 127.66 KiB | 58 KiB/s, done.
|
|
Resolving deltas: 100% (283/283), done.
|
|
project_name [Project Name]: Reddit Clone
|
|
project_slug [reddit_clone]: reddit
|
|
author_name [Daniel Roy Greenfeld]: Daniel Greenfeld
|
|
email [you@example.com]: pydanny@gmail.com
|
|
description [A short description of the project.]: A reddit clone.
|
|
domain_name [example.com]: myreddit.com
|
|
version [0.1.0]: 0.0.1
|
|
timezone [UTC]: America/Los_Angeles
|
|
use_whitenoise [y]: n
|
|
use_celery [n]: y
|
|
use_mailhog [n]: n
|
|
use_sentry_for_error_reporting [y]: y
|
|
use_opbeat [n]: y
|
|
use_pycharm [n]: y
|
|
windows [n]: n
|
|
use_python3 [y]: y
|
|
use_docker [y]: n
|
|
use_heroku [n]: y
|
|
use_compressor [n]: y
|
|
Select postgresql_version:
|
|
1 - 9.5
|
|
2 - 9.4
|
|
3 - 9.3
|
|
4 - 9.2
|
|
Choose from 1, 2, 3, 4 [1]: 1
|
|
Select js_task_runner:
|
|
1 - Gulp
|
|
2 - Grunt
|
|
3 - None
|
|
Choose from 1, 2, 3, 4 [1]: 1
|
|
use_lets_encrypt [n]: n
|
|
Select open_source_license:
|
|
1 - MIT
|
|
2 - BSD
|
|
3 - GPLv3
|
|
4 - Apache Software License 2.0
|
|
5 - Not open source
|
|
Choose from 1, 2, 3, 4, 5 [1]: 1
|
|
use_elasticbeanstalk_experimental: n
|
|
|
|
Enter the project and take a look around::
|
|
|
|
$ cd reddit/
|
|
$ ls
|
|
|
|
Create a git repo and push it there::
|
|
|
|
$ git init
|
|
$ git add .
|
|
$ git commit -m "first awesome commit"
|
|
$ git remote add origin git@github.com:pydanny/redditclone.git
|
|
$ git push -u origin master
|
|
|
|
Now take a look at your repo. Don't forget to carefully look at the generated README. Awesome, right?
|
|
|
|
For local development, see the following:
|
|
|
|
* `Developing locally`_
|
|
* `Developing locally using docker`_
|
|
|
|
.. _options: http://cookiecutter-django.readthedocs.io/en/latest/project-generation-options.html
|
|
.. _`Developing locally`: http://cookiecutter-django.readthedocs.io/en/latest/developing-locally.html
|
|
.. _`Developing locally using docker`: http://cookiecutter-django.readthedocs.io/en/latest/developing-locally-docker.html
|
|
|
|
Community
|
|
-----------
|
|
|
|
* Have questions? **Before you ask questions anywhere else**, please post your question on `Stack Overflow`_ under the *cookiecutter-django* tag. We check there periodically for questions.
|
|
* If you think you found a bug or want to request a feature, please open an issue_.
|
|
* For anything else, you can chat with us on `Gitter`_.
|
|
|
|
.. _`Stack Overflow`: http://stackoverflow.com/questions/tagged/cookiecutter-django
|
|
.. _`issue`: https://github.com/pydanny/cookiecutter-django/issues
|
|
.. _`Gitter`: https://gitter.im/pydanny/cookiecutter-django?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge
|
|
|
|
For Readers of Two Scoops of Django 1.8
|
|
--------------------------------------------
|
|
|
|
You may notice that some elements of this project do not exactly match what we describe in chapter 3. The reason for that is this project, amongst other things, serves as a test bed for trying out new ideas and concepts. Sometimes they work, sometimes they don't, but the end result is that it won't necessarily match precisely what is described in the book I co-authored.
|
|
|
|
For pyup.io Users
|
|
-----------------
|
|
|
|
If you are using `pyup.io`_ to keep your dependencies updated and secure, use the code *cookiecutter* during checkout to get 15% off every month.
|
|
|
|
.. _`pyup.io`: https://pyup.io
|
|
|
|
"Your Stuff"
|
|
-------------
|
|
|
|
Scattered throughout the Python and HTML of this project are places marked with "your stuff". This is where third-party libraries are to be integrated with your project.
|
|
|
|
Releases
|
|
--------
|
|
|
|
Need a stable release? You can find them at https://github.com/pydanny/cookiecutter-django/releases
|
|
|
|
|
|
Not Exactly What You Want?
|
|
---------------------------
|
|
|
|
This is what I want. *It might not be what you want.* Don't worry, you have options:
|
|
|
|
Fork This
|
|
~~~~~~~~~~
|
|
|
|
If you have differences in your preferred setup, I encourage you to fork this to create your own version.
|
|
Once you have your fork working, let me know and I'll add it to a '*Similar Cookiecutter Templates*' list here.
|
|
It's up to you whether or not to rename your fork.
|
|
|
|
If you do rename your fork, I encourage you to submit it to the following places:
|
|
|
|
* cookiecutter_ so it gets listed in the README as a template.
|
|
* The cookiecutter grid_ on Django Packages.
|
|
|
|
.. _cookiecutter: https://github.com/audreyr/cookiecutter
|
|
.. _grid: https://www.djangopackages.com/grids/g/cookiecutters/
|
|
|
|
Submit a Pull Request
|
|
~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
We accept pull requests if they're small, atomic, and make our own project development
|
|
experience better.
|
|
|
|
Articles
|
|
---------
|
|
|
|
* `Development and Deployment of Cookiecutter-Django on Fedora`_ - Jan. 18, 2016
|
|
* `Development and Deployment of Cookiecutter-Django via Docker`_ - Dec. 29, 2015
|
|
* `How to create a Django Application using Cookiecutter and Django 1.8`_ - Sept. 12, 2015
|
|
* `Introduction to Cookiecutter-Django`_ - Feb. 19, 2016
|
|
* `Django and GitLab - Running Continuous Integration and tests with your FREE account`_ - May. 11, 2016
|
|
|
|
Have a blog or online publication? Write about your cookiecutter-django tips and tricks, then send us a pull request with the link.
|
|
|
|
.. _`Development and Deployment of Cookiecutter-Django via Docker`: https://realpython.com/blog/python/development-and-deployment-of-cookiecutter-django-via-docker/
|
|
.. _`Development and Deployment of Cookiecutter-Django on Fedora`: https://realpython.com/blog/python/development-and-deployment-of-cookiecutter-django-on-fedora/
|
|
.. _`How to create a Django Application using Cookiecutter and Django 1.8`: https://www.swapps.io/blog/how-to-create-a-django-application-using-cookiecutter-and-django-1-8/
|
|
.. _`Introduction to Cookiecutter-Django`: http://krzysztofzuraw.com/blog/2016/django-cookiecutter.html
|
|
.. _`Django and GitLab - Running Continuous Integration and tests with your FREE account`: http://dezoito.github.io/2016/05/11/django-gitlab-continuous-integration-phantomjs.html
|
|
|
|
Code of Conduct
|
|
---------------
|
|
|
|
Everyone interacting in the Cookiecutter project's codebases, issue trackers, chat
|
|
rooms, and mailing lists is expected to follow the `PyPA Code of Conduct`_.
|
|
|
|
Support This Project
|
|
---------------------------
|
|
|
|
This project is maintained by volunteers. Support their efforts by spreading the word about:
|
|
|
|
Two Scoops Press
|
|
~~~~~~~~~~~~~~~~~~
|
|
|
|
.. image:: https://cdn.shopify.com/s/files/1/0304/6901/t/2/assets/logo.png?11985289740589874793
|
|
:name: Two Scoops Press
|
|
:align: center
|
|
:alt: Two Scoops Press
|
|
:target: https://twoscoopspress.com
|
|
|
|
Two Scoops Press brings you the best dairy-themed Django references in the universe
|
|
|
|
pyup
|
|
~~~~~~~~~~~~~~~~~~
|
|
|
|
.. image:: https://pyup.io/static/images/logo.png
|
|
:name: pyup
|
|
:align: center
|
|
:alt: pyup
|
|
:target: https://pyup.io/
|
|
|
|
Pyup brings you automated security and dependency updates used by Google and other organizations. Free for open source projects!
|
|
|
|
.. _`PyPA Code of Conduct`: https://www.pypa.io/en/latest/code-of-conduct/
|