mirror of
https://github.com/DRYTRIX/TimeTracker.git
synced 2026-01-05 19:20:21 -06:00
98728691ef
- Add Task model with full CRUD operations, status tracking, and priority management - Integrate tasks with existing projects and time entries via foreign key relationships - Create new Flask routes (/tasks) with admin and user role-based access control - Implement task status transitions (pending → in_progress → completed → cancelled) - Add task filtering by status, priority, assignee, and project - Create responsive Jinja2 templates for task listing, creation, editing, and viewing - Integrate task selection in timer and manual time entry forms - Add task management to project dashboards and navigation menus - Implement automatic database migration system for seamless deployment - Create migration scripts to add missing tables and columns - Update startup script to detect and run migrations automatically - Add comprehensive error handling and validation - Include full documentation (TASK_MANAGEMENT_README.md) - Update project structure and main README with new feature details Database Changes: - New 'tasks' table with indexes for performance - Add 'task_id' column to 'time_entries' table - Automatic migration detection and execution Technical Implementation: - SQLAlchemy relationships with proper backrefs and cascading - Flask-Login integration for role-based access - Bootstrap 5 responsive UI components - Font Awesome icons for visual enhancement - Comprehensive test coverage and error handling This feature enables users to break down projects into manageable tasks, track progress, assign work, and maintain better project organization.
Docker Database Initialization
This directory contains scripts and configuration for the TimeTracker Docker setup with automatic database initialization.
Overview
The Docker setup now includes automatic database connection checking and initialization:
- Database Connection Check: The app waits for the PostgreSQL database to be ready
- Initialization Check: Verifies if the database has the required tables
- Automatic Initialization: If needed, runs the Python initialization script to create tables and default data
Files
start.sh
Main startup script that:
- Waits for database connection
- Checks if database is initialized
- Runs initialization if needed
- Starts the Flask application
init-database.py
Python script that:
- Connects to the database
- Creates all required tables using SQLAlchemy models
- Creates default admin user, settings, and project
- Handles errors gracefully
test-db.py
Utility script to test database connectivity and show initialization status.
init.sql and init-db.sh
Legacy initialization scripts (kept for reference, not used by default).
How It Works
- Docker Compose starts the PostgreSQL container
- Health Check ensures PostgreSQL is ready
- App Container waits for database to be healthy
- Startup Script checks database connection
- Initialization Check verifies required tables exist
- Python Script creates tables and default data if needed
- Flask App starts normally
Environment Variables
The following environment variables are used:
DATABASE_URL: PostgreSQL connection stringADMIN_USERNAMES: Comma-separated list of admin usernamesTZ: Timezone settingCURRENCY: Currency settingROUNDING_MINUTES: Time rounding setting
Testing
To test the database setup manually:
# Test database connection and status
docker exec timetracker-app python /app/docker/test-db.py
# Manually initialize database (if needed)
docker exec timetracker-app python /app/docker/init-database.py
Troubleshooting
Database Connection Issues
- Check if PostgreSQL container is running:
docker ps - Check PostgreSQL logs:
docker logs timetracker-db - Verify environment variables are set correctly
Initialization Issues
- Check app container logs:
docker logs timetracker-app - Verify database permissions
- Check if tables exist:
docker exec timetracker-db psql -U timetracker -d timetracker -c "\dt"
Health Check Failures
- Ensure the
/_healthendpoint is accessible - Check if the app is binding to the correct port
- Verify network connectivity between containers