Summary

Added a security warning notice to the Docker deployment section of the README.md to educate users about secure handling of sensitive information in production deployments.

Changes Made

• Added a GitHub-flavored markdown admonition block with [!WARNING] immediately after the Docker deployment instructions
• Positioned the notice before the "Database Requirements" section for optimal visibility
• Included comprehensive security guidance covering secrets, credentials, and environment variables

Security Notice Content

The warning advises users to:

• Never commit sensitive secrets, credentials, or production environment variables to the repository
• Use Docker secrets, environment variables, or secure secrets managers for production deployments
• Follow security best practices to keep applications and data safe

Rationale

This addition helps prevent common security vulnerabilities by:

1. Raising awareness about the risks of committing secrets to version control
2. Providing clear guidance on secure deployment practices
3. Promoting security best practices within the developer community
4. Positioning the warning strategically in the deployment section where users are most likely to need this information

The notice is placed in the Docker section specifically because this is where users would be setting up production deployments and handling sensitive configuration.

Visual Impact

The warning uses GitHub's built-in admonition syntax (> [!WARNING]) which renders as a visually distinct yellow warning box in GitHub's interface, ensuring high visibility and user attention.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.