How hhyo/archery works
Project Type and Purpose
• Archery is a web-based SQL auditing and query platform. Its primary purpose is to provide a user interface for running SQL queries, performing audit reviews, executing amendments, and managing database tasks.
• The README and overall repository structure indicate that it supports multiple database backends (MySQL, MariaDB, MsSQL, Oracle, etc.), along with features like data dictionary generation, slow log processing, and session management.
• It leverages several external tools (goInception for SQL auditing; SOAR for SQL optimization; etc.), making it a complex, service-oriented application.
Analyzing the File Structure
• The top-level directories show multiple components:
• The "archery" directory contains Django’s core settings and URL configuration files (asgi.py, settings.py, urls.py, wsgi.py) which indicates the main entry point for the Django application.
• The “common” directory holds authentication logic, middleware, dashboard utilities, templates, static resources, and utility modules. This is the shared code used application-wide.
• The “sql” directory and “sql_api” sub-directory include modules specific to SQL auditing, workflows, execution, and APIs exposing these services.
• The “src” and “docker-compose” folders indicate Dockerfiles, Kubernetes charts, and deployment scripts – showing how the application is containerized and orchestrated.
• There are clear separations of concerns with different modules, suggesting an MVC-like pattern managed by Django and an API layer that might be separately leveraged by external clients.
• Use clear and concise labels for each component (e.g., “Web Client”, “Django Application Server”, “SQL Workflow Module”, “External Database Connectors”, “Docker/Container Infrastructure”).
• Another style for deployment/infrastructure components (Docker, Kubernetes/Helm charts).
• Detail external integrations (e.g., goInception, SQLAdvisor) and show how these connect to the SQL auditing module.
• Optionally, include labels for asynchronous operations (queues or scheduled tasks) and how they interact with the primary workflow.