How valyrian24052/tag works
Project type and purpose
• This is a full-stack, containerized Python web application (“Tag”), acting as a WIP AI personal assistant.
• The frontend is a simple Quart-served HTML/CSS interface; the backend is a Quart app in Python that calls Azure Cognitive Services (AI).
• Infrastructure is defined in Bicep files for Azure Container Apps, Container Registry, monitoring, and security roles.
• CI/CD is handled by GitHub workflows building, testing, and deploying the container.
File structure
• src/
• Dockerfile, .dockerignore, gunicorn.conf.py
• quartapp/ with chat.py, static/, templates/
• requirements.txt
• infra/
• main.bicep, parameters
• core/ai/cognitiveservices.bicep
• core/host/* (container-app, container-apps-environment, registry)
• core/monitor/loganalytics.bicep
• core/security (registry-access, role)
• docker-compose.yaml for local multi-container dev
• .devcontainer for VS Code remote dev
• GitHub workflows (.github/workflows) for lint, test, Azure Bicep validation, Docker build/deploy
• tests/ for pytest, snapshot tests of the chat streams
README
• Confirms it’s an AI personal assistant using “Tag” name.
Detail and essential elements
• Registry, Container-Apps-Environment, Security Role, Log Analytics, Cognitive Services.
• Separate concerns:
• Code (src/) vs. infra (infra/) vs. tests vs. CI vs. local dev.