How mrmonkey09/requerimientos_de_sistema works
Project type and purpose
• This is a full-stack, multi-tenant content management system (CMS) built with Django (Python).
• The README only contains the title “Requerimientos_de_Sistema,” but the file tree shows a Django project named cms_multitenant with apps for core functionality (main), media management (media_files), and tenant isolation (tenants).
File structure
Top-level:
• cms_multitenant/ – the Django project root.
• cms_multitenant/cms_project/ – settings, URL routing, WSGI/ASGI entrypoints.
• cms_multitenant/manage.py – Django CLI entry.
• cms_multitenant/templates/ – HTML templates for views.
• cms_multitenant/staticfiles/ & static/ – collected static assets (CSS, JS, images).
• cms_multitenant/media/ & cms_multitenant/media_files/ – user-uploaded content storage and Django app for managing media.
• cms_multitenant/populate_data.py – data seeding script.
• .gitignore, .gitattributes, VSCode workspace settings, etc.
Key apps inside cms_project:
– main: core pages, models for properties, views/templates for home, about, contact, property listings.
– media_files: models/views for uploaded media assets.
– tenants: middleware, custom auth backend, admin overrides to enforce tenant data isolation.
Configuration & deployment hints:
– settings.py: database config, static & media settings, middleware stack.
– asgi.py/wsgi.py: server entrypoints.
– urls.py: URL dispatcher.