Update entrypoint in docker-compose for Langfuse MinIO

[asdek]

Description of the Change

Problem

The MinIO service configuration in docker-compose-langfuse.yml had issues with environment variable interpolation and command execution in the entrypoint script. The original configuration used incorrect syntax for shell variables and command substitution, which caused Docker Compose to fail during startup.

Solution

The changes include:

1. Changed the entrypoint syntax from > to | to properly handle multiline shell scripts
2. Fixed environment variable references by using proper shell variable syntax
3. Corrected command substitution syntax for process management
4. Improved code formatting and comments for better maintainability

Closes #9

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• 🚀 New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📚 Documentation update
• 🔧 Configuration change
• 🧪 Test update
• 🛡️ Security update

Areas Affected

• Core Services (Frontend UI/Backend API)
• AI Agents (Researcher/Developer/Executor)
• Security Tools Integration
• Memory System (Vector Store/Knowledge Base)
• Monitoring Stack (Grafana/OpenTelemetry)
• Analytics Platform (Langfuse)
• External Integrations (LLM/Search APIs)
• Documentation
• Infrastructure/DevOps

Testing and Verification

Test Configuration

PentAGI Version: latest
Docker Version: 28.0.1
Host OS: darwin 24.3.0
LLM Provider: N/A
Enabled Features: [Langfuse]

Test Steps

1. Stop any running Langfuse containers
2. Apply the changes to docker-compose-langfuse.yml
3. Start the services using docker-compose -f docker-compose-langfuse.yml up -d
4. Verify MinIO service starts successfully
5. Check MinIO bucket creation and configuration

Test Results

The MinIO service now starts correctly with proper environment variable interpolation and command execution. The bucket is created and configured as expected.

Security Considerations

No security implications as this is a configuration fix that maintains existing security settings.

Performance Impact

No performance impact as this is a configuration fix that improves reliability.

Documentation Updates

• README.md updates
• API documentation updates
• Configuration documentation updates
• GraphQL schema updates
• Other:

Deployment Notes

No special deployment considerations. The changes are backward compatible and maintain existing environment variable structure.

Checklist

Code Quality

• My code follows the project's coding standards
• I have added/updated necessary documentation
• I have added tests to cover my changes
• All new and existing tests pass
• I have run go fmt and go vet (for Go code)
• I have run npm run lint (for TypeScript/JavaScript code)

Security

• I have considered security implications
• Changes maintain or improve the security model
• Sensitive information has been properly handled

Compatibility

• Changes are backward compatible
• Breaking changes are clearly marked and documented
• Dependencies are properly updated

Documentation

• Documentation is clear and complete
• Comments are added for non-obvious code
• API changes are documented

Additional Notes

The changes are focused on fixing the MinIO service configuration in the Langfuse stack. The modifications improve reliability and maintainability without affecting the core functionality or security of the system.