Files
michaelschiemer/docs/todo
Michael Schiemer 36ef2a1e2c
Some checks failed
🚀 Build & Deploy Image / Determine Build Necessity (push) Failing after 10m14s
🚀 Build & Deploy Image / Build Runtime Base Image (push) Has been skipped
🚀 Build & Deploy Image / Build Docker Image (push) Has been skipped
🚀 Build & Deploy Image / Run Tests & Quality Checks (push) Has been skipped
🚀 Build & Deploy Image / Auto-deploy to Staging (push) Has been skipped
🚀 Build & Deploy Image / Auto-deploy to Production (push) Has been skipped
Security Vulnerability Scan / Check for Dependency Changes (push) Failing after 11m25s
Security Vulnerability Scan / Composer Security Audit (push) Has been cancelled
fix: Gitea Traefik routing and connection pool optimization
- Remove middleware reference from Gitea Traefik labels (caused routing issues)
- Optimize Gitea connection pool settings (MAX_IDLE_CONNS=30, authentication_timeout=180s)
- Add explicit service reference in Traefik labels
- Fix intermittent 504 timeouts by improving PostgreSQL connection handling

Fixes Gitea unreachability via git.michaelschiemer.de
2025-11-09 14:46:15 +01:00
..

Todo Lists

This directory contains detailed todo lists for various framework features and improvements.

Active Todo Lists

High Priority

  • Currently no high-priority items

Medium Priority

  • css-generation-system.md - Comprehensive CSS generation from PHP components
    • Status: Planning Phase
    • Effort: Large (2-3 weeks)
    • Decision needed on architecture approach

Low Priority

Todo List Guidelines

File Structure

Each todo list should include:

  • Status: Planning / In Progress / Blocked / Completed
  • Priority: High / Medium / Low
  • Estimated Effort: Small / Medium / Large (with time estimate)
  • Context: Why this todo exists
  • Phases: Organized breakdown of tasks
  • Decision Log: Key decisions to make
  • Notes: Advantages, challenges, open questions
  • Related Files: Existing and to-be-created files

Task Format

  • Task Title - Brief description
    • Additional details
    • File references
    • Dependencies

Status Indicators

  • [ ] - Todo (not started)
  • [x] - Done (completed)
  • [~] - In Progress
  • [!] - Blocked (waiting on decision/dependency)

Updating Todos

  • Update Last Updated date when making changes
  • Mark completed tasks with [x]
  • Add notes about decisions made
  • Link to relevant PRs or commits when tasks are completed

Creating New Todo Lists

When creating a new todo list:

  1. Use descriptive filename: feature-name.md
  2. Include all sections from the template
  3. Add entry to this README
  4. Link from relevant documentation
  5. Discuss with team if high priority

Completed Todo Lists

Completed todo lists are moved to docs/todo/completed/ for reference.


Last Updated: 2025-10-19