Django mbedakake rong jinis file: static files (aset sing dadi bagian saka aplikasinmu — CSS, JavaScript, gambar sing kowe kapal) lan media files (file sing ditunggal dening pengguna saat runtime — foto profil, dokumen). Dheweke ditangani kanthi beda-beda amarga sumber lan siklus urip dheweke beda-beda sakabehane.
STATIC_URL =
STATICFILES_DIRS = [BASE_DIR / ]
STATIC_ROOT = BASE_DIR /
<!-- in templates -->
{% load static %}
<link rel="stylesheet" href="{% static 'css/style.css' %}">
<img src="{% static 'images/logo.png' %}">
Static files iku bagian saka codebase mu — CSS, JS, font, gambar desain. Dheweke dikontrol versi, padha kanggo kabeh pengguna, lan diserve saka direktori static proyekmu.
python manage.py collectstatic
# gathers ALL static files (from your apps and STATICFILES_DIRS) into STATIC_ROOT,
# so a web server / CDN can serve them efficiently in production
Ng produksi, collectstatic nggabungake static files saka kabeh app menyang siji direktori (STATIC_ROOT) supaya web server utawa CDN bisa diserve — Django ora diserve dheweke dhewe ing produksi.
# settings.py
MEDIA_URL = "/media/"
MEDIA_ROOT = BASE_DIR / "media" # where UPLOADED files are stored
# a model with an uploadable file
class Profile(models.Model):
avatar = models.ImageField(upload_to="avatars/") # stored under MEDIA_ROOT/avatars/
document = models.FileField(upload_to="docs/")
profile.avatar.url # the URL to access the uploaded file
Media files iku ditunggal dening pengguna saat runtime nganggo FileField/ImageField. Dheweke dinamis, ORA ing version control, lan banjir seiring wektu amarga pengguna ngunggal konten.
Static files Media files
Source part of your code uploaded by users at runtime
Version control YES (committed) NO (user-generated, .gitignored)
Lifecycle fixed (changes with code) dynamic (grows continuously)
Examples CSS, JS, logos, fonts avatars, uploaded documents, photos
Settings STATIC_URL/ROOT/DIRS MEDIA_URL/ROOT
Production collectstatic + CDN/server stored on disk/cloud (S3), served carefully
✓ Static → serve via the web server (nginx) or a CDN (cached, fast)
✓ Media → store on cloud storage (S3) for scalability/persistence; in multi-server
setups, local disk doesn't work (files must be shared) → use S3/object storage
✓ Security → VALIDATE uploaded files (type, size); be careful serving user uploads
(a user could upload malicious content)
Ngerteni bedane static lawan media iku penting kanggo mbangun lan deploy aplikasi Django kanthi bener, amarga rong jinis file iki nduweni sumber, siklus urip, lan cara panganan sing beda-beda sakabehane. Static files (CSS, JavaScript, gambar, font sing duweku aplikasinmu) iku bagian saka codebase, dikontrol versi, lan padha kangga kabeh — direferensi nganggo {% static %} lan digabungake nganggo collectstatic kanggo produksi diserve dening web server utawa CDN. Media files (tunggalan pengguna nganggo FileField/ImageField) iku konten dinamis sing digawe pengguna, dibuat saat runtime, ORA ing version control, lan terus banjir.
Nggabung-gabungake dheweke utawa salah konfigurasi pengaturan (STATIC_* lawan MEDIA_*) iku sumber umum saka "CSS ku ora muatan" utawa "tunggalan ora gawé" masalah, utamané ing produksi ing ngendi Django ora diserve static files dhewe (mbutuhake collectstatic lan server/CDN sing pas).
Bedane iki uga nduweni implikasi produksi lan keamanan: media files ing deployment multi-server ora bisa mung ngandelake disk lokal (kudu nganggo panyimpenan awan kabeh kaya S3), lan tunggalan pengguna mbutuhake validasi (jenis file, ukuran) lan diserve kanthi ati-ati supaya ora ana resiko keamanan saka konten jahat.
Nangerteni cara konfigurasi lan tangani rong jinis, peran collectstatic, lan pertimbangan produksi (CDN kanggo static, panyimpenan awan kanggo media, keamanan tunggalan) iku pangetan praktis sing asring dibutuhake kanggo mbangun lan deploy aplikasi Django kanthi bener — penghalang umum sing pangatan iki ngatasi.