Adopt Podman Cloud Run deployment pattern

[stevei101]

Summary

• adopt podman-cloudrun-deploy-gha workflow for backend/frontend deploys
• reorganize docs into deployment/integrations/archive and add cloud run migration plan
• convert docs/build tooling to bun-only usage and fix lint/test warnings

Testing

• bun run lint
• bun run test -- --run
• uv run pytest backend/tests

[gemini-code-assist]

Summary of Changes

Hello @stevei101, 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 focuses on modernizing and standardizing the project's deployment infrastructure and development tooling. By adopting a shared Podman Cloud Run deployment pattern via GitHub Actions, the project aims to achieve more consistent and efficient deployments for both its backend and frontend services. Concurrently, the documentation has been reorganized for better accessibility, and the frontend development environment has been streamlined by migrating to Bun as the sole package manager, enhancing developer experience and build performance.

Highlights

• Cloud Run Deployment Standardization: The project now adopts a standardized Podman Cloud Run deployment pattern using a shared GitHub Actions workflow (podman-cloudrun-deploy-gha) for both backend and frontend services, streamlining the deployment process.
• Documentation Restructuring: The docs directory has been significantly reorganized into deployment, integrations, and archive subdirectories, improving clarity and maintainability of project documentation. Several old hackathon and strategy documents have been moved to the archive folder.
• Bun-only Tooling Migration: Frontend build and development tooling has been converted to use bun exclusively, removing npm references from documentation and package.json, and fixing related lint/test warnings.
• Deployment Test Updates: Existing deployment-related tests have been updated and refactored to verify the new shared Cloud Run deployment workflow, ensuring correct configuration of service names, container ports, regions, and environment variables.
• Merge Conflict Resolution: Resolved merge conflict markers in backend/models/stream_event_model.py, cleaning up the codebase.

Ignored Files

• Ignored by pattern: .github/workflows/** (2)
  • .github/workflows/build.yml
  • .github/workflows/cloud-run-deploy.yml

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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

This pull request successfully adopts the podman-cloudrun-deploy-gha shared workflow, which is a great move for standardizing deployments. The reorganization of the documentation into deployment, integrations, and archive folders improves clarity, and the switch to bun for all frontend tooling is a welcome simplification. The code changes, including lint fixes and test updates, are well-executed.

My main concern, as detailed in a specific comment, is the removal of test suites that verified important security and deployment best practices for the FastAPI application and Docker configuration. While the CI-related tests have been updated appropriately, losing these other checks could introduce regressions in the future. I recommend reconsidering their removal.