Django configuration tana zaune a settings.py, amma aikace-aikacen gaske suna buƙatar saita daban-daban ga kowane muhalli (haɓakawa, tsaftacewa, aiki) kuma dole ne su rike sirri daga kodaddi. Sarrafa haka daidai shine duka bukatuwa na aiki da bukatuwa na tsaro.
settings.py
DEBUG =
SECRET_KEY =
DATABASES = {: {: }}
Rikicewa da qiyi na ƙari yana haɗa muhalli da — sananniya — yana watsa sirri (SECRET_KEY, kalmar siri ta database, APIssans) cikin sarrafa juzu'i, matsala masu bahaya sosai.
import os
from pathlib import Path
SECRET_KEY = os.environ["DJANGO_SECRET_KEY"] # from the environment, NOT code
DEBUG = os.environ.get("DJANGO_DEBUG", "False") == "True"
ALLOWED_HOSTS = os.environ.get("ALLOWED_HOSTS", "").split(",")
DATABASES = {
"default": {
"ENGINE": "django.db.backends.postgresql",
"NAME": os.environ["DB_NAME"],
"PASSWORD": os.environ["DB_PASSWORD"], # injected per environment
}
}
# tools like django-environ / python-decouple make this cleaner (+ .env file support)
Karanta saita (musamman sirri) daga environment variables yana rike shi daga kodaddi — kabannin kodaddi guda yana aiki a kowane muhalli tare da saita daban-daban da aka toshe (hanyar masu gida goma sha biyu).
settings/
base.py # shared settings (apps, middleware, templates)
development.py # from base import *; DEBUG=True, local DB, debug toolbar
production.py # from base import *; DEBUG=False, security hardening, real DB
test.py # test-specific settings
# production.py
from .base import *
DEBUG = False
ALLOWED_HOSTS = ["example.com"]
SECURE_SSL_REDIRECT = True # production-only security settings
# select via: DJANGO_SETTINGS_MODULE=config.settings.production
Keɓewar saita zuwa base.py da saita kowa ba koli ba (zabin ta DJANGO_SETTINGS_MODULE) yana keɓe daidai saita da ta muhalli tare da baji saitun gama gari.
DEBUG = False # ❗ NEVER True in production — leaks sensitive error info
ALLOWED_HOSTS = ["example.com"] # required when DEBUG=False
SECRET_KEY = os.environ[...] # strong, secret, from the environment
# + SECURE_SSL_REDIRECT, SESSION_COOKIE_SECURE, HSTS, etc. for hardening
✓ NEVER commit secrets — use env vars / a secret manager; gitignore .env
✓ DEBUG=False in production (DEBUG=True leaks tracebacks, settings → security risk)
✓ Commit a .env.example documenting required variables (no real values)
Sarrafa saita a cikin muhalli daban-daban shine duka bukatuwan sarrafa aiki da aikin tsaro mafi mahimmanci ga kowane aikace-aikacen Django na gaske.
Aikace-aikace dole ne su nai daban-daban a cikin muhalli — haɓakawa yana buƙatar DEBUG=True da saita gida masu sauƙi, yayin da aiki yana buƙatar DEBUG=False, sarrafa tsaro, database na gaske, da hosts daidai — kuma settings.py guda da aka fi rodi ba zai iya saida duka waɗannan.
Mafi mahimmanci, wannan bukatuwa mahimmanci ta tsaro ce: rikicewa da sirri (SECRET_KEY, kalmar siri ta database, APIssans) yana watsa su cikin sarrafa juzu'i, ɗaya daga cikin yawaita da mahimmanci sosai tsaron rashin tsabtacewa (kowa da hannu a repositori, ko a repositori jama'a, yana karɓa mabuɗi don aikace-aikace da bayanka).
Jiyo mabugit — karanta saita da sirri daga environment variables (rike shi daga kodaddi, hanyar masu gida goma sha biyu, akai lokaci da kayan aiki kamar django-environ da fayil .env da aka nufe) da keɓewar saita zuwa baji da saita kowa ba koli ba — ke mahimmanci ne don watsa Django cikin tsaro da daidai.
Jiyo saitan aiki mahimmanci (musamman cewa DEBUG dole ne su kasua False a aiki, saboda DEBUG=True yana fallasa tracer, jiyoye kodaddi, da saita ga masu yin rikici, tare da ALLOWED_HOSTS da sarrafa tsaro) shine bakin baki na ilimi na aiki.
Jigon saita sarrafa daidai — sirri a muhalli, saita da ta muhalli daidai, tsabtaccen aiki — shine asali na yin aiki da aikace-aikace Django cikin inganci da guje wa calami mahimmanci da suka zo daga sirri da aka fallasa ko muhalli da aka tsara rashin daidai, saida haka mahimmanci, ilimi na amfani ne da mahimmanci sosai ga kowane aikin aiki na gaske.