Multi-Container Docker Compose Document Management System

.dockerignore

@@ -0,0 +1,65 @@
+# Git
+.git
+.gitignore
+
+# Documentation
+documentation/
+README.md
+*.md
+
+# Environment files
+.env
+.env.local
+.env.*.local
+
+# Node.js (if any frontend dependencies exist)
+node_modules/
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+
+# Python cache
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+
+# IDE files
+.vscode/
+.idea/
+*.swp
+*.swo
+*~
+
+# OS files
+.DS_Store
+.DS_Store?
+._*
+.Spotlight-V100
+.Trashes
+ehthumbs.db
+Thumbs.db
+
+# Logs
+logs
+*.log
+
+# Docker
+docker-compose.override.yml
+Dockerfile.dev

.env.example

@@ -1,14 +1,36 @@
-# Clerk Authentication
-NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=pk_test_xxxxxx
-CLERK_SECRET_KEY=sk_test_xxxxxx
+# Database Configuration
+POSTGRES_DB=dms_db
+POSTGRES_USER=dms_user
+POSTGRES_PASSWORD=dms_password
+DATABASE_URL=postgresql://dms_user:dms_password@database:5432/dms_db
 
-# Supabase
-NEXT_PUBLIC_SUPABASE_URL=your_project_url
-NEXT_PUBLIC_SUPABASE_ANON_KEY=your_anon_key
+# Redis Configuration
+REDIS_URL=redis://cache:6379/0
+REDIS_HOST=cache
+REDIS_PORT=6379
 
-# Stripe (Optional)
-STRIPE_SECRET_KEY=sk_test_xxxxx
-NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY=pk_test_xxxxx 
+# Celery Configuration
+CELERY_BROKER_URL=redis://cache:6379/0
+CELERY_RESULT_BACKEND=redis://cache:6379/0
 
-# OpenAI
-OPENAI_API_KEY=sk_test_xxxxx
+# Frontend (Laravel) Configuration
+APP_ENV=local
+APP_DEBUG=true
+APP_URL=http://localhost:8000
+DB_HOST=database
+DB_PORT=5432
+DB_DATABASE=dms_db
+DB_USERNAME=dms_user
+DB_PASSWORD=dms_password
+
+# Backend API Configuration
+BACKEND_URL=http://backend:8000
+API_HOST=0.0.0.0
+API_PORT=8000
+
+# Shared Storage Paths
+INPUT_FOLDER_PATH=/app/shared/input
+OUTPUT_FOLDER_PATH=/app/shared/output
+
+# Docker Compose Project Name
+COMPOSE_PROJECT_NAME=dms

CLAUDE.md

@@ -0,0 +1,64 @@
+# Codespace Task Management Guide
+
+## Documentation Available
+
+📚 **Project Documentation**: Check the documentation files in this directory for project-specific setup instructions and guides.
+**Project Tasks**: Check the tasks directory in documentation/tasks for the list of tasks to be completed. Use the CLI commands below to interact with them.
+
+## MANDATORY Task Management Workflow
+
+🚨 **YOU MUST FOLLOW THIS EXACT WORKFLOW - NO EXCEPTIONS** 🚨
+
+### **STEP 1: DISCOVER TASKS (MANDATORY)**
+You MUST start by running this command to see all available tasks:
+```bash
+task-manager list-tasks
+```
+
+### **STEP 2: START EACH TASK (MANDATORY)**
+Before working on any task, you MUST mark it as started:
+```bash
+task-manager start-task <task_id>
+```
+
+### **STEP 3: COMPLETE OR CANCEL EACH TASK (MANDATORY)**
+After finishing implementation, you MUST mark the task as completed, or cancel if you cannot complete it:
+```bash
+task-manager complete-task <task_id> "Brief description of what was implemented"
+# or
+task-manager cancel-task <task_id> "Reason for cancellation"
+```
+
+## Task Files Location
+
+📁 **Task Data**: Your tasks are organized in the `documentation/tasks/` directory:
+- Task JSON files contain complete task information
+- Use ONLY the `task-manager` commands listed above
+- Follow the mandatory workflow sequence for each task
+
+## MANDATORY Task Workflow Sequence
+
+🔄 **For EACH individual task, you MUST follow this sequence:**
+
+1. 📋 **DISCOVER**: `task-manager list-tasks` (first time only)
+2. 🚀 **START**: `task-manager start-task <task_id>` (mark as in progress)
+3. 💻 **IMPLEMENT**: Do the actual coding/implementation work
+4. ✅ **COMPLETE**: `task-manager complete-task <task_id> "What was done"` (or cancel with `task-manager cancel-task <task_id> "Reason"`)
+5. 🔁 **REPEAT**: Go to next task (start from step 2)
+
+## Task Status Options
+
+- `pending` - Ready to work on
+- `in_progress` - Currently being worked on  
+- `completed` - Successfully finished
+- `blocked` - Cannot proceed (waiting for dependencies)
+- `cancelled` - No longer needed
+
+## CRITICAL WORKFLOW RULES
+
+❌ **NEVER skip** the `task-manager start-task` command
+❌ **NEVER skip** the `task-manager complete-task` command  (use `task-manager cancel-task` if a task is not planned, not required, or you must stop it)
+❌ **NEVER work on multiple tasks simultaneously**
+✅ **ALWAYS complete one task fully before starting the next**
+✅ **ALWAYS provide completion details in the complete command**
+✅ **ALWAYS follow the exact 3-step sequence: list → start → complete (or cancel if not required)**