Skip to content
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

Move to Bitnami Based Postgres Image #61

Closed
wants to merge 2 commits into from

Conversation

hofq
Copy link
Contributor

@hofq hofq commented Jan 20, 2024

Resolves #55

Currently, this chart uses the Bitnami PG subchart, which is made for the Bitnami PG Image. This Connectivity Allows for Easy Operation, as all in the Bitnami Chart Documented Functions also worked with the Immich Deployment.

Since the Change to pgvecto.rs in #53 and the related Image Change, this Compatibility no longer exists, which leads to some undocumented Breaks of Databases and Errors.

To restore features from that Bitnami Deployment, I added a pipeline based off @SoarinFerret `s Dockerfile, which Builds an pgvecto.rs version of the Official Bitnami Image on Chart release, with the PG Version in the values.yaml file, and the pgvecto.rs version in the Dockerfile.

hofq and others added 2 commits January 20, 2024 20:57
* Add Pipeline for PG Image

* Add Pipeline for PG Image

* Replace Tag with Branch Trigger

* fix path

* Move psql img Version into a seperate Job

* Test Handling of Environment Vars inside of a single Job

* Update build-and-push Tag Var

* Fix pgvecto Folder

* Fix Script Context

* Update bitnami-tag.sh permissions

* Fix Script Context

* Add Dockerfile Path

* Replace Env with Templating Section

* Add full Image path to tag var

* Consolidate Workflow Files

* Switch Image Name

* Update Image Testing Name

---------

Co-authored-by: hofq <[email protected]>
@samholton
Copy link
Contributor

Would this upgrade from existing tensorchord/pgvecto-rs:pg14-v0.1.11 or be a breaking change and require manual database migration?

@bo0tzz
Copy link
Member

bo0tzz commented Dec 19, 2024

Superseded by #150

@bo0tzz bo0tzz closed this Dec 19, 2024
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.

v1.91.0 DB Crash
3 participants