How adeyosemanputra/pygoat works
Project type & purpose
– PyGoat is a monolithic Django web application that serves intentionally vulnerable OWASP-Top-Ten security training labs.
– It ships with multiple “apps” (Django modules) under a single codebase (e.g. introduction/, challenge/), plus a set of self-contained “dockerized labs” each in its own container.
– Extras include a Jupyter-based chatbot (chatbot/pygoatbot.ipynb) and CLI utilities (PyGoatBot.py, installer/uninstaller scripts).
File-structure hints at architecture
Top-level:
• pygoat/ – the Django project (settings, URLs, WSGI/ASGI)
• introduction/, challenge/ – core Django apps following MVC (models, views, templates, migrations)
• dockerized_labs/… – a folder of sub-directories, each with its own Dockerfile, small web app (Flask or Django) and docker-compose.yml (broken_auth_lab, insec_des_lab, etc.)
• manage.py & challenge/management/commands – management-command pattern for DB population
• Dockerfile, docker-compose.yml, Procfile – containerization and deployment scripts
• Solutions/, docs/ – static markdown for solution guides and developer docs
README confirms tech stack & deployment modes
• Django (Python)
• Local run via manage.py runserver or Gunicorn behind Heroku (Procfile)
• Docker container & Docker Compose support
• Database (configurable, e.g. SQLite locally or PostgreSQL in Docker production)
• No external microservice dependencies beyond Docker labs