cookiecutter-django | An opinionated Cookiecutter template for Django

I am starting a project with cookiecutter-django with docker deployment, for some reason traefik can't get letsencrypt certificate, this is the error:

I'm using Caprover with Docker to run a Django project (Django-Cookiecutter) which is non persistent. I'm also running a persistent app on the same server which imports csv data. I need the two apps to basically share a file together. This is how i imagined it:

1. The importer app imports csv data and stores it as a json file inside a specific folder.
2. The Django app accesses the json file in that folder and uses a script i wrote to import the json into the database. I'm struggling to understand how i can access the folder inside my importer app containing the json file from my django app. Does anyone have an idea on how i can make this happen between those two docker containers?

Context
In my Django project (based on Django cookiecutter) I use django-graphql-auth which depends on django-graphql-jwt.
I forked django-graphql-jwt to make some changes so then also forked django-graphql-auth to update its dependency to my django-graphql-jwt fork:

I’m sure this is pretty straightforward to someone experienced. I’m learning Django through the Wedge of Django ebook.

I’m using Python 3.8.7 installed via pyenv like so: pyenv install 3.8.7

Then I’ve set up a virtualenv like so: pyenv virtualenv 3.8.7 everycheese

I activate the virtualenv in my repo like so: pyenv local everycheese

The environment is shown as active in the prompt, as it starts with (everycheese).

The main project is cloned from Django Cookiecutter https://github.com/cookiecutter/cookiecutter-django

I’ve then used pip to install requirements from the requirements.txt files.

However - I’m running into trouble when I try to add new packages (by adding the package to requirements.txt as a new line and installing again with pip).

pip list, or pip freeze both show the new module. But when I add the module to my INSTALLED_APPS and try to import it in my models.py file, Django cannot find it.

When I type which python, and which pip, they point to different directories and I think this may be part of the problem but I am stuck.

Cookiecutter-django have endpoints /auth-token/ to get a token and /api/users/me/ for getting user info. But it does not seem to have a logout endpoint. Am I right?

And, if the serverside logout is needed, i will need to write it.

Can you confirm? Thanks.

How does running docker-compose -f local.yml up create the postgres database in the postgres container with configurations in .envs/.local/.postgres. I have looked through the Dockerfiles and cannot seem to find a command such as createdb except in the maintenance/restore file.

Cookiecutter-django: https://github.com/pydanny/cookiecutter-django

I recently updated a django api from 2.2 to 3.1. I updated the dockerfile and related bash files like django-cookiecutter did https://github.com/pydanny/cookiecutter-django/commit/b22045bcd4ebf563ccdcf226fb389a6bb71e2654#diff-1872e6a6f0bbcb27f2eda185ac89eed05eb7a402b298e58bcbef29bf039c2c13

The upgrade mostly went well except now in production we cannot send email. I have a minimal management command I run in production to test email settings

Can anyone help me with to configure my django cookiecutter production setup to work with Gmail SMTP.

I have deployed my application using docker. Cookiecutter gives you to configure your app to anymail providers. I've chosen Mailgun however I didn't have an email address that has been verified by my domain provider. So, I couldn't register any user to my app because ( https://cookiecutter-django.readthedocs.io/en/latest/deployment-with-docker.html#configuring-the-stack) here it says you can't :)

I have tried to override the default email verification setting from "mandatory" to "none". However, it still threw 500. In below, I've added all-auth settings. I had to decide either to buy an email address or configure my app to work with Gmail Smtp or get rid of this email verification process.

settings/base.py

We're applying Black code style to a django project.

In all the tutorials / examples I find (such as in django cookiecutter and this blog), I keep seeing django's migrations files excluded from the linter.

But to my mind, these are still python files. Sure, django may not autogenerate them to meet the Black spec. But it's not like developers always write their code to meet Black spec... that's what linting is for!

Why would migration files be considered different to any other python files?!

NB I'm aware of the possibility of changing an already-applied migration if you've got pre-existing migrations - this requires care on first application (as does first application to the rest of the codebase, frankly) but surely isn't a reason not to do it?

EDIT - @torxed asked for an example of a django migration file

I'm not sure how helpful this'll be tbh, but a typical django migration file might look like this (in this case adding a char field to a table):