Book Image

Becoming an Enterprise Django Developer

By : Michael Dinder
Book Image

Becoming an Enterprise Django Developer

By: Michael Dinder

Overview of this book

Django is a powerful framework but choosing the right add-ons that match the scale and scope of your enterprise projects can be tricky. This book will help you explore the multifarious options available for enterprise Django development. Countless organizations are already using Django and more migrating to it, unleashing the power of Python with many different packages and dependencies, including AI technologies. This practical guide will help you understand practices, blueprints, and design decisions to put Django to work the way you want it to. You’ll learn various ways in which data can be rendered onto a page and discover the power of Django for large-scale production applications. Starting with the basics of getting an enterprise project up and running, you'll get to grips with maintaining the project throughout its lifecycle while learning what the Django application lifecycle is. By the end of this book, you'll have learned how to build and deploy a Django project to the web and implement various components into the site.
Table of Contents (15 chapters)
1
Part 1 – Starting a Project
5
Part 2 – Django Components
10
Part 3 – Advanced Django Components

Chapter 6: Exploring the Django Admin Site

This chapter will introduce the Django admin site, which is a feature allowing developers to register certain models into a model-centric interface where only permitted users can manage database content. This feature is designed to read the metadata related to models as well as the fields and field constraints set on those models to build a set of pages that search, sort, filter, create, edit, and delete records found in those tables.

The admin site is an optional feature of the Django framework that can be used in projects. It allows us to use user-based roles and permission settings that are built into the Django framework, allowing only permitted users to edit, add, or delete objects. User roles can be modified to only grant permission to edit certain models and can even be set to a granular level, such as only letting a user edit or view data but not add or delete data. This feature can be deactivated if it is not desired or needed...