How paulocoutinhox/pyaa works
Project type and purpose
• This is a full-stack, monolithic Django application template (“PyAA – Python Advanced Application”) meant to bootstrap web sites, e-commerce platforms or SaaS products.
• Key features (from README): user & subscription management, credit & checkout system, banner & content management, multi-language, static content, admin reports, background queue (DjangoQ), cron jobs, Stripe & email integration, Docker support.
File structure
• Top-level “manage.py” and “pyaa/” folder define the Django project (settings/dev.py, settings/prod.py, urls.py, wsgi/asgi).
• “apps/” contains all domain apps (backup, banner, content, customer, gallery, language, newsletter, report, shop, site, system_log, user, web). Each app follows Django’s MVC (models, views, serializers, urls, migrations, tests).
• “templates/” & “apps/web/static/” contain the frontend layer (server-side templates, SASS/CSS, JS, images).
• Dockerfile(s), nginx.conf, and entrypoint scripts define containerized web and cron environments.
• “extras/production” and “docs/” cover deployment, database, queue, cron, Stripe, security, etc.
README for additional insights
• Technology stack: Python, Django, Django REST (serializers, API docs), DjangoQ (background queue), PostgreSQL/MySQL (DB), Stripe (payments), Recaptcha, uWSGI + Nginx, Docker.
• Architectural patterns: Monolithic MVC with clear app‐module separation; background workers & cron for async/periodic tasks; REST API endpoints; server‐side rendering with optional client‐side JS.