feat: Add Docker Compose setup option

[keenranger]

Description

Thank you for opening a Pull Request!
Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

• Follow the CONTRIBUTING Guide.
• Make your Pull Request title in the https://www.conventionalcommits.org/ specification.
  • Important Prefixes for release-please:
    • fix: which represents bug fixes, and correlates to a SemVer patch.
    • feat: represents a new feature, and correlates to a SemVer minor.
    • feat\!:, or fix\!:, refactor\!:, etc., which represent a breaking change (indicated by the \!) and will result in a SemVer major.
• Ensure the tests and linter pass (Run nox -s format from the repository root to format)
• Appropriate docs were updated (if necessary)

Adds Docker Compose support for simplified deployment.

Changes

• Add docker-compose.yml that builds from GitHub repository
• Update README with Docker Compose as third run option

Testing

Tested docker compose up -d - application runs correctly on http://127.0.0.1:8080

🦕

[gemini-code-assist]

Summary of Changes

Hello @keenranger, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the deployment flexibility of the application by introducing a Docker Compose setup. This new option streamlines the process of getting the application up and running, particularly for users who prefer a containerized environment without the need for manual Docker image builds, thereby improving ease of use and accessibility.

Highlights

• New Deployment Option: Introduced Docker Compose support, offering a simplified method for deploying and running the application without manual image building.
• Documentation Update: The README.md has been updated to include detailed instructions for using the new Docker Compose setup, making it a third primary option for running the application.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

The pull request introduces Docker Compose as a new option for running the A2A Inspector, simplifying the deployment process. The changes include adding a docker-compose.yml file and updating the README with instructions on how to use Docker Compose. I've suggested minor improvements to the README to enhance clarity for users unfamiliar with Docker Compose.