-
-
Notifications
You must be signed in to change notification settings - Fork 218
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
feat: add postgres support + migrations #628
base: develop
Are you sure you want to change the base?
Conversation
Merge 'origin/develop' into main
Merge develop into main
Merge 'develop' into main
Merge develop into main
…ed ssl for postgres config Fallenbagel#186
Whats the difference between this and #421? |
This PR contains all the changes in #421 plus changes from @ralgar that are also mentioned in that PR. Additionally, this PR contains the migration script required to get postgres running, documentation on how to configure postgres, and improved ssl configuration options |
I've been using this branch for a couple months and semi-regularly get these two errors in my Postgres logs.
This one seems to be because there is no value provided for the |
This pull request has merge conflicts. Please resolve the conflicts so the PR can be successfully reviewed and merged. |
Keen to get this merged. Has been working great for me. Jumped over from overseerr just for this postgres support. Edit: Also, hope this isn't being held up because of any potential issues with migrating from sqlite to postgres. It should be the radarr/lidarr/sonarr/whisparr (etc) approach, where they officially support new instances with postgres and only offer some suggestions for migrating to postgres with no official support (see: https://wiki.servarr.com/radarr/postgres-setup).
|
Same. What's blocking a merge appart from an obvious rebase..? |
CHANGELOG.md
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove this file from this pr
server/utils/DbColumnHelper.ts
Outdated
import { Column } from 'typeorm'; | ||
|
||
const pgTypeMapping: { [key: string]: ColumnType } = { | ||
datetime: 'timestamp with time zone', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe it's best practice to always store time in db without the timezones
I added some review comments long ago. Forgot to submit it lol. Also our focus for now is to get #815 in |
This pull request has merge conflicts. Please resolve the conflicts so the PR can be successfully reviewed and merged. |
…nto v1.7.0/postgresql # Conflicts: # README.md # yarn.lock
I know that this is not the current priority to get in, but do we have even a hand wave idea of potentially how long it may be? I can continue to use the preview container but I am eagerly awaiting this not being a preview feature :) |
Is there a timeframe to merge this? Since running in kubernetes this is a deal breaker for now |
Chiming in to say, I migrated from Overseerr to Jellyseerr for this. I'm also running in Kubernetes, and I'm trying to move everything I can to postgres. |
I’d like to add this to my docker stack as well. Quite keen to have it working with Postgres |
Description
Screenshot (if UI-related)
To-Dos
yarn build
yarn i18n:extract
Issues Fixed or Closed
TODO:
drcarrot/jellyseerr-postgres:latest