Skip to content

For consuming projects

Paste one of these into the Django or Pulumi project that depends on pulumi-django-azure so agents know what this package does without inventing behavior.

## Azure deployment (pulumi-django-azure)

This project is deployed with [`pulumi-django-azure`](https://django-azu.re).
Treat the following as the deployment and runtime contract (do not invent Azure or CI behavior outside it):

- Full docs for LLMs: https://django-azu.re/llms-full.txt
- Index: https://django-azu.re/llms.txt
- Scope (what the package owns): https://django-azu.re/scope/

Pulumi imports (infra project):
`from pulumi_django_azure.django_deployment import DjangoDeployment, HostDefinition`

Django imports (app project):
`from pulumi_django_azure.settings import *` and optional `patch_django_settings_for_azure`.
RQ cron (when `django_rq_cron=True`): `from pulumi_django_azure.cron import register_task`
with a `@task` Task — never plain `rq.cron.register` under the default django-tasks worker.

Minimal: index only

Deployment contract for this app: https://django-azu.re/llms.txt

Cursor rule snippet (consumer repo)

---
description: Azure deploy contract via pulumi-django-azure
alwaysApply: true
---

# pulumi-django-azure

This app’s Azure infra, App Service build/startup, and Azure Django settings are provided by
`pulumi-django-azure`. Prefer https://django-azu.re/llms-full.txt over guessing.

- Pulumi: import from `pulumi_django_azure.django_deployment` only.
- Django: use `pulumi_django_azure.settings` / middleware / management commands as documented.
- RQ cron: use `pulumi_django_azure.cron.register_task` with `@task` Tasks (not plain `rq.cron.register`).
- Do not invent DNS or CDN HTTPS enablement as automatic package steps (Postgres Entra app principals are created automatically by the package bootstrap Function unless disabled).

Human docs

Site: https://django-azu.re Source: GitLab PyPI: pulumi-django-azure