amerkurev / django-docker-template

Dockerized Django with Postgres, Gunicorn, and Traefik or Caddy (with auto renew Let's Encrypt)

Hi there 👋

I'm a Python Developer and the creator of the website python.study, as well as some interesting Python projects.

I also write articles about Python on Medium.

My recent posts:

• Creating a Powerful Interactive CLI App with ChatGPT in Python
• Subtle Aspects of Python's Generator Function
• Download large file in Python with beautiful progress bar

In addition, I have a rich experience in C++ development from the past, and I dabble a bit in Go as well.

And when the need arises, and there's no one else to help, I can also write in JavaScript, although my main focus is backend development.

django-docker-template's Issues

Migrate from Traefik and Nginx to one Caddy

Using a custom user model when starting a project

Django recommends setting up a custom user model when starting a new project. It's easy to add in the beginning but becomes more of a hurdle later on. Thoughts on adding it in?

https://docs.djangoproject.com/en/4.2/topics/auth/customizing/#using-a-custom-user-model-when-starting-a-project

no issues, i just wanted to thank you

DJANGO_SECURE_SSL_REDIRECT set to true in docker-compose.tls.yml

This setting is mentioned in settings.py SECURE_SSL_REDIRECT = is_true(os.getenv('DJANGO_SECURE_SSL_REDIRECT')). However the env file does not have a var for it.

Traefik - dashboard

Thanks for all the work on this project, its awesome!

I was wondering if there is any tips you may have for adding the traefik dashboard to the project.

I'm currently working from this: https://blog.creekorful.org/2020/01/how-to-expose-traefik-2-dashboard-securely-docker-swarm/

Traefik dashboard

Is the dashboard enabled in dev/prod? If so how can it be accessed?

Env file for prod

Hi! I appreciate you putting this together and publishing it. I am going to prod with a new site using this. I typically use env files in local and prod that are not checked in to git. I prevent this by adding all .en* files to gitignore. How are you handling secrets? I wish your project was a little more opinionated on this. If I overwrite the settings in .env, i would have to handle them not getting updated when I pull changes into prod. If I create a new .env-prod file that is not checked in to git, I would have to update references to the existing .env file with something like "if SETTINGS.DEBUG use .env else use .env-prod". Am I missing something?

SQL Choice Conflict in Readme

"The technology stack used includes:

[....]
PostgreSQL ver. 15
[...]"

and

"Another important point is the use of SQLite3 instead of Postgres (which we don't run). In our example, we add a volume named sqlite. This data is stored persistently and does not disappear between restarts of the Django development server. However, if you have a second similar project, it would be better to change the volume name from sqlite to something else so that the second project uses its own copy of the database. For example:"

It's very likely that I'm simply missing something here but these seems to be an editing mistake.

Permission Issues When Running Docker Containers

I encountered two permission issues while running containers with Docker on Fedora 38. Here are the details of the problems and the solutions I applied:

1- Issue with permission to access docker.sock

When I ran the following command:

docker compose -f docker-compose.debug.yml up

I encountered the following error:

"msg="Failed to retrieve information of the docker client and server host: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock"

To resolve this, I added privileged: true to the reverse-proxy YAML configuration in the docker-compose.debug.yml file.

2- Issue with permission to access source files in development container
When I ran the following command:

docker run -it --rm -p 8000:8000 -v sqlite:/sqlite -v $(pwd)/website:/website django-docker-template:master python manage.py runserver 0.0.0.0:8000

I encountered the following error:

"python: can't open file '/usr/src/website/manage.py': [Errno 13] Permission denied"

To resolve this, I had to change /usr/src/website to /usr/src/website:z everywhere in the YAML files and the command.

Environment:

• Fedora 38
• Docker 20.10.23
• docker-compose 1.29.2.