Docker Support for Issue Docker Support #85

[SANTHOSH-SACHIN]

Docker Support for Data Formulator

Overview

This PR adds comprehensive Docker support to Data Formulator, enabling easier deployment and development. The implementation includes multi-stage builds, environment variable management, and production-ready configurations.

Key Changes

• Added multi-stage Dockerfile optimized for both development and production
• Implemented docker-compose.yml for simplified deployment
• Added docker-entrypoint.sh with production/development mode support
• Enhanced environment variable handling for API keys and configuration
• Updated documentation with Docker setup instructions

Features

• Multi-stage Build: Optimized image size by separating frontend build from runtime
• Environment Management: Flexible configuration through environment variables
• Development Mode: Volume mounting for live code updates
• Production Mode: Gunicorn support for production deployments
• API Key Management: Secure handling of provider API keys

Documentation Updates

• Added Docker deployment instructions to README.md
• Created comprehensive DOCKER.md guide
• Updated DEVELOPMENT.md with Docker workflow
• Added configuration documentation

Related Files

• Dockerfile
• docker-compose.yml
• docker-entrypoint.sh
• DOCKER.md
• Updated README.md and DEVELOPMENT.md

Dependencies

• Python 3.12
• Node.js 18
• Required Python packages in requirements.txt
• Frontend dependencies in package.json

Security Considerations

• API keys managed through environment variables
• No sensitive data in Docker images
• Production-ready Gunicorn configuration
• Proper permission handling in containers

Breaking Changes

None. This is an additive change that maintains backward compatibility with existing deployment methods.

Future Work

• Container orchestration support (Kubernetes)
• Additional deployment environment configurations
• CI/CD pipeline integration
  @Chenglong-MS @danmarshall

[SANTHOSH-SACHIN]

@microsoft-github-policy-service agree

[danmarshall]

Thanks for the PR, but we already have an existing PR for this: #90 . Would you mind looking at that one and let us know how this differs?