Skip to content

Conversation

@vibhatha
Copy link
Member

This PR includes the following

  • Evaluating Supabase and Neon for Postgres DB as a service
  • Docker compose yaml for production setting testing
  • Updating internal docs

This PR closes #444

…remote databases, along with a deployment guide and a Supabase restore script.
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @vibhatha, I'm Gemini Code Assist1! 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 facilitates the evaluation and testing of remote database services within a production-like Docker Compose environment. It introduces a new Docker Compose configuration that connects to external managed databases like Supabase, MongoDB Atlas, and Neo4j Aura, along with comprehensive documentation for setup and troubleshooting. Additionally, a utility script is provided to streamline the restoration of PostgreSQL backups to Supabase.

Highlights

  • Remote Database Evaluation: This PR includes an evaluation of Supabase and Neon for PostgreSQL as a service, moving towards managed database solutions.
  • Production Docker Compose Setup: A new Docker Compose configuration has been added specifically for testing production settings, utilizing remote database connections.
  • Internal Documentation Update: New internal documentation has been created to guide users on deploying the application in a production-like environment with remote databases.
  • PostgreSQL Backup Restoration Script: A new script is introduced to automate the process of restoring PostgreSQL database backups from a GitHub repository to a Supabase instance.
  • .gitignore Update: The .gitignore file has been updated to include .env.* patterns, preventing environment-specific configuration files from being committed.
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.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a production-like Docker Compose setup for using remote databases, along with a script to restore a Postgres database to Supabase. The changes are well-structured.

My review includes a critical security fix for the database restore script to prevent password exposure, and a cleanup suggestion for the new Docker Compose file to improve maintainability. Please see the detailed comments for suggestions.


## Prerequisites

* Docker Desktop (or Docker Engine + Compose plugin) installed.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Docker Desktop or Rancher Desktop?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh I will fix this.
It is Rancher.

Copy link
Collaborator

@zaeema-n zaeema-n left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks fine to me

@vibhatha vibhatha merged commit 13a6393 into LDFLK:main Jan 26, 2026
4 checks passed
@vibhatha vibhatha deleted the feat-eval-supabase branch January 26, 2026 08:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Eval] Remote DB Usage via Docker Compose

2 participants