Frontend Components

The Django Prodserver skill provides a unified interface for managing production processes within a Django project, abstracting the complexity of starting various backend servers and task workers. It is designed for backend developers and DevOps engineers who need a consistent, reliable way to execute production-grade environments, including Gunicorn, Granian, Uvicorn, Waitress, Celery, and Django-Q2. By leveraging a centralized PRODUCTION_PROCESSES configuration in settings.py, this skill allows for clean separation between development and deployment logic, ensuring that processes are started with the correct parameters every time.

• Standardized management command interface (python manage.py prodserver <process_name>) for diverse backends.

• Built-in support for high-performance servers like Gunicorn, Granian, and Uvicorn with automated argument formatting from dictionary configurations.

• Native integration for background task processing via Celery and Django-Q2.

• Extensible architecture through BaseServerBackend subclassing, enabling the implementation of custom server wrappers for specific infrastructure needs.

• Automatic validation and configuration of task queues, such as checking for the existence of django_q in INSTALLED_APPS and proper module string resolution for Celery applications.

• Users should define the PRODUCTION_PROCESSES dictionary in their Django settings.py to map process names to their specific BACKEND classes and ARGS configurations.

• Input configuration allows for passing raw strings or mapped dictionaries for server arguments, which the skill automatically serializes into command-line flags (e.g., --bind=0.0.0.0:8111).

• The skill is intended to bridge the gap between local development processes and containerized production orchestration, reducing the cognitive load of maintaining multiple disparate start scripts.

• Ensure all required dependencies (such as Gunicorn, Celery, or Granian) are installed in the production environment before executing the respective backend via the prodserver command.

• For custom backends, implement the start_server method and optionally override prep_server_args to handle specific default flag injection or argument sanitization.