Urtzi Alfaro c9246dec25 Add Modify button handler to enable PO editing from dashboard
Problem:
- The "Modify" button in the Action Queue (Panel de Control) did nothing when clicked
- Previously removed handleModify function and onModify prop during earlier refactoring
- Users couldn't open the purchase order modal in edit mode from the dashboard

Solution:
- Added handleModify function that sets poModalMode to 'edit' before opening modal
- Updated handleViewDetails to explicitly set mode to 'view' for clarity
- Passed onModify handler to ActionQueueCard component

How it works:
- View button -> Opens modal in view mode (read-only)
- Modify button -> Opens modal in edit mode (editable fields)
- Both use the same PurchaseOrderDetailsModal component
- Modal's initialMode prop controls which mode is shown first

Now users can:
- Click "View Details" to see PO information
- Click "Modify" to edit priority, delivery date, notes, and product quantities
- See real-time updates as they edit quantities and prices

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-18 12:14:13 +01:00
2025-11-14 07:23:56 +01:00
2025-11-02 20:24:44 +01:00
2025-11-18 07:17:17 +01:00
2025-11-18 07:17:17 +01:00
2025-07-17 14:34:24 +02:00
2025-11-14 20:27:39 +01:00
2025-09-23 12:49:35 +02:00
2025-11-06 11:04:50 +01:00
2025-11-15 21:21:06 +01:00

🍞 Bakery IA - Multi-Service Architecture

Welcome to Bakery IA, an advanced AI-powered platform for bakery management and optimization. This project implements a microservices architecture with multiple interconnected services to provide comprehensive bakery management solutions.

🚀 Quick Start

Prerequisites

  • Docker Desktop with Kubernetes enabled
  • Docker Compose
  • Node.js (for frontend development)

Running the Application

  1. Clone the repository:

    git clone <repository-url>
    cd bakery-ia
    
  2. Set up environment variables:

    cp .env.example .env
    # Edit .env with your specific configuration
    
  3. Run with Docker Compose:

    docker-compose up --build
    
  4. Or run with Kubernetes (Docker Desktop):

    # Enable Kubernetes in Docker Desktop
    # Run the setup script
    ./scripts/setup-kubernetes-dev.sh
    

🏗️ Architecture Overview

The project follows a microservices architecture with the following main components:

  • Frontend: React-based dashboard for user interaction
  • Gateway: API gateway handling authentication and routing
  • Services: Multiple microservices handling different business domains
  • Infrastructure: Redis, RabbitMQ, PostgreSQL databases

🐳 Kubernetes Infrastructure

🛠️ Services

The project includes multiple services:

  • Auth Service: Authentication and authorization
  • Tenant Service: Multi-tenancy management
  • Sales Service: Sales processing
  • External Service: Integration with external systems
  • Training Service: AI model training
  • Forecasting Service: Demand forecasting
  • Notification Service: Notifications and alerts
  • Inventory Service: Inventory management
  • Recipes Service: Recipe management
  • Suppliers Service: Supplier management
  • POS Service: Point of sale
  • Orders Service: Order management
  • Production Service: Production planning
  • Alert Processor: Background alert processing

📊 Monitoring

The system includes comprehensive monitoring with:

  • Prometheus for metrics collection
  • Grafana for visualization
  • ELK stack for logging (planned)

🚀 Production Deployment

For production deployment on clouding.io with Kubernetes:

  1. Set up your clouding.io Kubernetes cluster
  2. Update image references to your container registry
  3. Configure production-specific values
  4. Deploy using the production kustomization:
    kubectl apply -k infrastructure/kubernetes/environments/production/
    

🤝 Contributing

  1. Fork the repository
  2. Create a feature branch
  3. Make your changes
  4. Submit a pull request

🔧 Troubleshooting

macOS "too many open files" error

If you encounter the "too many open files" error when running the application on macOS:

failed to create fsnotify watcher: too many open files

This is related to system limits on file system watchers. The kind configuration has been updated to handle this, but if you still encounter issues:

  1. Restart your Kind cluster with the updated configuration:

    kind delete cluster --name bakery-ia-local
    kind create cluster --config kind-config.yaml --name bakery-ia-local
    
  2. If needed, you can also increase the macOS system limits (though this shouldn't be necessary with the updated kind configuration):

    # Check current limits
    sysctl kern.maxfiles kern.maxfilesperproc
    
    # These are usually set high enough by default, but if needed:
    # sudo sysctl -w kern.maxfiles=65536
    # sudo sysctl -w kern.maxfilesperproc=65536
    

📄 License

This project is licensed under the MIT License.

Description
Main repository for Bakery IA project - Automatically created
Readme 20 MiB
Languages
Python 56.3%
TypeScript 39.6%
Shell 2.9%
CSS 0.4%
Starlark 0.3%
Other 0.3%