Skip to content

Provide options for an external Postgres #3662

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
williamdes opened this issue Apr 15, 2025 · 1 comment
Open

Provide options for an external Postgres #3662

williamdes opened this issue Apr 15, 2025 · 1 comment

Comments

@williamdes
Copy link
Contributor

Problem Statement

As a user I prefer to run myself the Postgres and Clickhouse DBs.
It also makes me sure the DB servers still run when I down/up Sentry.

A lot of the setup relies onto having Postgres as a container for upgrades.
Can an external option be done ?
Same for Clickhouse but much less a priority.

Solution Brainstorm

Currently I comment out the Postgres container and tweaks envs.
And also have to comment all your upgrade lines, and check on each new release. (this is quite the most problematic)

Solution: ask Sentry itself for a DB connection with Python and run the migration ?

@aldy505
Copy link
Collaborator

aldy505 commented Apr 16, 2025

I'm gonna backlog this and have a debate with @BYK about doing a documentation vs providing a .patch file 😆

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Status: No status
Development

No branches or pull requests

2 participants