fix(platform): Add local enc key

[aarushik93]

Background

Changes 🏗️

Testing 🔍

Note

Only for the new autogpt platform, currently in autogpt_platform/

• Create from scratch and execute an agent with at least 3 blocks
• Import an agent from file upload, and confirm it executes correctly
• Upload agent to marketplace
• Import an agent from marketplace and confirm it executes correctly
• Edit an agent from monitor, and confirm it executes correctly

Configuration Changes 📝

Note

Only for the new autogpt platform, currently in autogpt_platform/

If you're making configuration or infrastructure changes, please remember to check you've updated the related infrastructure code in the autogpt_platform/infra folder.

Examples of such changes might include:

• Changing ports
• Adding new services that need to communicate with each other
• Secrets or environment variable changes
• New or infrastructure changes such as databases

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 Security concerns Sensitive information exposure: The PR introduces a hardcoded encryption key (ENCRYPTION_KEY=dvziYgz0KSK8FENhju0ZYi8-fRTfAdlz6YLhdB_jhNw=) in the docker-compose file. While there's a comment indicating it should not be used in production, hardcoding sensitive information in configuration files is a security risk. This key could potentially be used to decrypt sensitive data if it falls into the wrong hands. It's recommended to use environment variables or secure secret management solutions to handle such sensitive information, especially for production environments.

⚡ Recommended focus areas for review Security Concern The PR introduces a hardcoded encryption key in the docker-compose file. This practice is not recommended for production environments and should be reviewed carefully.