cookiecutter/cookiecutter-django

Support Matrix

Open

#1052 opened on Feb 25, 2017

View on GitHub
 (3 comments) (4 reactions) (0 assignees)Python (10,896 stars) (2,713 forks)batch import
docshelp wanted

Description

Cookiecutter Django is loaded with features. Not all of them work on every environment out of the box, or we don't have docs for it.

It'd great if we had a matrix that shows what feature is supported on what environment:

Development

Vanilla Python (mac) Vanilla Python (Linux) Vanilla Python (windows) Docker (mac) Docker (windows) Docker (Linux)
postgres
mailhog
grunt
gulp
pycharm

Production

Ubuntu Docker Heroku Elastic Beanstalk Python Anywhere
postgres
redis
celery
grunt
gulp
whitenoise
static files
lets encrypt
compressor

Is someone able to help out and fill (parts) of this matrix?

Contributor guide

Tech stack
pythondocker
Domain
documentationbackend
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Knowledge of Django environmentsAbility to test on multiple OSesDocker experience
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
This issue requests a support matrix for features across development and production environments. To start, examine the existing documentation in the repository for currently known supported configurations. Then, test each feature (e.g., PostgreSQL, MailHog, Grunt) on each platform by running the Cookiecutter Django template and checking for errors or missing functionality. Update the matrix based on test results. Contributors should comment on the issue to coordinate efforts and avoid duplicate work.