Django Managed Database Planning

How it works

For a service such as Amazon RDS, choose supported engine versions, private network access, a restricted database role and a verified TLS certificate chain. Keep security-group rules narrow instead of opening the database to every address. The course does not create an AWS account, purchase a resource or connect to RDS. This local example checks an allowlisted configuration policy with fictional endpoint data; it does not prove network or certificate validity.

Run in the supplied local Django project

This lesson uses Django 5.2.18 LTS with Python 3.12. Download the source downloader and run node download-project.mjs http://127.0.0.1:8000 with Node 22 while previewing locally. It creates a new bhylu-django-lab folder and refuses to overwrite an existing one. After deployment, the default base is bhylu.com; until then use your local preview URL.

Inside that new folder, create a virtual environment, install requirements.txt and run the complete lesson file shown below. Every lesson creates a fresh in-memory SQLite database and temporary upload storage. It does not edit the interactive lab’s db.sqlite3 or Bhylu’s database. The visible listing below is the lesson’s core code; its complete downloaded file includes the shared bootstrap.

Django does not run in Bhylu’s current browser playground. No Apache, MySQL or global PHP configuration change is needed. See the setup lesson for the full project and commands.

Example

Run .venv\Scripts\python.exe lessons\managed-database.py from the downloaded project root. Download the complete lesson file; keep it under lessons/. The project’s shared models, forms, views and fixture are prerequisites, not a hidden online runtime.

options = {"sslmode":"verify-full", "sslrootcert":"/trusted/provider-ca.pem"}
endpoint = "database.example.test"
print(options["sslmode"] == "verify-full")
print(endpoint.endswith(".example.test"))
print("sslrootcert" in options)

Expected result

True
True
True

The example names certificate verification as an explicit requirement and uses a reserved test hostname. Your actual CA path and endpoint must come from the selected provider’s current documentation and be verified in the real environment.