cookiecutter/cookiecutter-django
1
1
Fork 0
mirror of https://github.com/cookiecutter/cookiecutter-django.git synced 2024-09-21 03:19:07 +03:00
Code Issues Packages Projects Releases Wiki Activity

Update changelog for 2015-07-21

Browse Source
This commit is contained in:
Saurabh Kumar 2015-07-21 07:27:16 +05:30
parent 613b91d71e
commit 64119a093a
1 changed files with 10 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
changelog.md → CHANGELOG.md
View File

@ -2,14 +2,18 @@
All enhancements and patches to cookiecutter-django will be documented in this file. All enhancements and patches to cookiecutter-django will be documented in this file.
This project adheres to [Semantic Versioning](http://semver.org/). This project adheres to [Semantic Versioning](http://semver.org/).
## [2015-07-21]
## Changed
- memcached is as a cache is replace with redis (#258)(@burhan)
## [2015-07-18] ## [2015-07-18]
### Changed ### Changed
- Heroku deployment docs (@stepmr) - Heroku deployment docs (@stepmr)
- Heroku's free postgres tier is now "hobby-dev" - Heroku's free postgres tier is now "hobby-dev"
- pg:backups require a scheduled time - pg:backups require a scheduled time
- add missing Mailgun API key - add missing Mailgun API key
- Django recommends setting the PYTHONHASHSEED environment variable to random. See: https://docs.djangoproject.com/en/1.8/howto/deployment/checklist/#python-options - Django recommends setting the PYTHONHASHSEED environment variable to random. See: https://docs.djangoproject.com/en/1.8/howto/deployment/checklist/#python-options
- Use openssl to generate a secure, random secret_key - Use openssl to generate a secure, random secret_key
## [2015-07-17] ## [2015-07-17]