Chapter 1: Defining the Scope of a Django Standalone App
Chapter 2: Structuring Django Standalone Apps
Chapter 3: Testing
Chapter 4: Model Migrations
Chapter 5: Templates
Chapter 6: Using Static Files
Chapter 7: Namespacing in Your App
Chapter 8: Creating a Basic Package
Chapter 9: Scooping and Drawing Boundaries
Chapter 10: Separating Your App
Chapter 11: Adding Your App Back In
Chapter 12: Handling App Settings
Chapter 13: Internationalization
Chapter 14: Managing Version Compatibility
Chapter 15: Mixed Dependency Support
Chapter 16: Modularity
Chapter 17: Better Packaging
Chapter: 18: Licensing
Chapter: 19: Documenting Your Standalone App
Chapter 20: Additional Testing
Chapter 21: Automating
Chapter 22: Databases and other backend specific considerations
Chapter 23: Collaborating
Chapter 24: Using App Templates
Ben is cofounder of a web development consultancy and has been working professionally with Django for almost a decade. He has architected and led development on Django-based web applications including, custom content management systems, media platforms, and multi tenant back office solutions.
He lives in the Rochester, NY, area, and graduated from the University of Virginia with a degree in Economics. Previously he managed the data and analytics services for a market research firm and was an IT strategy consultant for a global management consulting firm. His own standalone apps include Django Organizations, a long term project for managing multi user accounts in Django projects.
Develop standalone Django apps to serve as the reusable building blocks for larger Django projects. This book explores best practices for publishing these apps, with special considerations for testing Django apps, and strategies for extracting existing functionality into a separate package.
This jumpstart reference is divided into four distinct and sequential sections, all containing short, engaging chapters that can be read in a modular fashion, depending on your level of experience. The first section covers the structure and scope of standalone Django apps. The second section digs into questions about pulling code out of existing projects and into new standalone apps for reuse. The third section details additional, advanced technical best practices toward making standalone apps as broadly useful as possible. The fourth and final section covers strategies for managing a published Django app.
Django Standalone Apps is the perfect resource for developers who have at least some prior experience working with Django web applications and want to simplify their deployments and share their knowledge as open source packages.
You will:
Scope a standalone Django app project for optimum usefulness
Extract code from existing projects to reuse
Test a standalone app outside of your Django project
Reuse your own code for increased delivery cadence and code quality
Review best practices for maintaining a Django app package