You're reading from Django in Production Expert tips, strategies, and essential frameworks for writing scalable and maintainable code in Django

Product type Paperback

Published in Apr 2024

Publisher Packt

ISBN-13 9781804610480

Length 348 pages

Edition 1st Edition

Languages

Python

Tools

Django

Concepts

Server Side Web Development

Author (1):

Arghya Saha

View More author details

Table of Contents (21) Chapters

Preface

1. Part 1 – Using Django and DRF to Build Modern Web Application

2. Chapter 1: Setting Up Django with DRF FREE CHAPTER

3. Chapter 2: Exploring Django ORM, Models, and Migrations

4. Chapter 3: Serializing Data with DRF

5. Chapter 4: Exploring Django Admin and Management Commands

6. Chapter 5: Mastering Django Authentication and Authorization

7. Part 2 – Using the Advanced Concepts of Django

8. Chapter 6: Caching, Logging, and Throttling

9. Chapter 7: Using Pagination, Django Signals, and Custom Middleware

10. Chapter 8: Using Celery with Django

11. Chapter 9: Writing Tests in Django

12. Chapter 10: Exploring Conventions in Django

13. Part 3 – Dockerizing and Setting Up a CI Pipeline for Django Application

14. Chapter 11: Dockerizing Django Applications

15. Chapter 12: Working with Git and CI Pipelines Using Django

16. Part 4 – Deploying and Monitoring Django Applications in Production

17. Chapter 13: Deploying Django in AWS

18. Chapter 14: Monitoring Django Application

19. Index

Why subscribe?

20. Other Books You May Enjoy

Working with the requirements.txt file

Different projects can have different dependency needs to run. That’s why we use the requirements.txt file to capture all the third-party packages installed and used in a project. But as projects grow, we can realize that some of the dependency packages are useful only while we are developing locally, some are useful in our CI pipeline, and some are used only for production. Hence it is important that we break our requirements.txt file into multiple parts.

We need to split our requirements.txt file into multiple files that would be used for different purposes. This is common in large projects and is always better to implement as soon as we create a new project. This ensures that only the actually used packages are shipped to production.

Here is a structure seen in most large projects: