godd0t/django-docker-quickstart

Your all-in-one Django-Docker starter kit. Pre-configured services including PostgreSQL, Redis, Celery, with Nginx and Traefik for production. Streamlined development with included tools for testing and formatting.

Hi there, I'm Lir Shala, aka godd0t 🙌

I'm a software engineer from the beautiful land of Kosovo 🇽🇰. I have more than half a decade of experience in the tech industry, working on various projects that showcase my skills and creativity. I have a solid foundation in computer science and a passion for developing software that is high-quality, scalable, and maintainable.

Python is my weapon of choice, where I have mastered the art of writing clean, efficient, and robust code that adheres to the best practices and standards. I have built web applications, data analysis tools, and more using Python and its rich ecosystem of libraries and frameworks. I'm also proficient in agile development methodologies and love working in dynamic, team-based environments. I value collaboration and innovation as the keys to success in any project.

If you're curious about me or want to get in touch, feel free to:

• Connect with me on LinkedIn
• Follow my thoughts on Medium
• Check out my Stack Overflow profile

django-docker-quickstart's Issues

make build-dev should use requirements.dev.txt

currently all builds use requirement.txt

Remove makemigrations in start.sh

Hi, and thanks for this template, very useful!

I'd like to suggest to remove the makemigrations command from start.sh script in production environment.

Usually, migrations should be generated on a local environment then versioned.
Otherwise, for example if you forget to run makemigrations in local, and then deploy, you'd have an unexpected behaviour.
That's why I think as a best practice, prod environment should only run migrate but not make migrations.

Feel free to disagree :)