Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Django in Production
  • Table Of Contents Toc
  • Feedback & Rating feedback
Django in Production

Django in Production

By : Arghya Saha
4.7 (9)
close
close
Django in Production

Django in Production

4.7 (9)
By: Arghya Saha

Overview of this book

You may have got your first Django developer job after a six-week bootcamp or online course, and that’s great, but what’s next? In small companies, mentorship can be hard to come by and gaining the traits of a senior developer without that can take a long time. This is precisely where Django in Production comes into play. This book will first delve into the true meaning of "good practice" and help you understand the rationale behind industry professionals building websites in specific ways to develop a solid foundation for your Django projects. Next, you will uncover hidden Django secrets through hands-on exploration, leveraging the power of Docker and version control to your advantage. You will gain insights into mastering Git hooks for efficient code maintenance, establishing a robust CI pipeline, and harnessing the capabilities of AWS Beanstalk. These tools will empower you to develop highly scalable products—an essential skill set for aspiring developers transitioning from junior to senior roles. Later, you will understand the significance of monitoring and be introduced to industry-standard tools utilized by professionals for effective monitoring practices. By the end of this book, you will have set yourself apart from the crowd, equipped with the knowledge and expertise to thrive as a seasoned Django developer.
Table of Contents (21 chapters)
close
close
1
Part 1 – Using Django and DRF to Build Modern Web Application
7
Part 2 – Using the Advanced Concepts of Django
13
Part 3 – Dockerizing and Setting Up a CI Pipeline for Django Application
16
Part 4 – Deploying and Monitoring Django Applications in Production

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:

  • requirements-base.txt – This file contains all the common third-party packages that are used in all the environments. For example, Django...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY