Skip to content

Conversation

danschmidt5189
Copy link
Contributor

@danschmidt5189 danschmidt5189 commented Oct 3, 2025

Integrates chainlit's official prisma data layer into the primary application image and tests it in the pipeline. This adds about 360M to the resulting image:

ghcr.io/berkeleylibrary/willa:latest 1.13GB
ghcr.io/berkeleylibrary/willa:AP-464-prisma_integration_refactoring 1.49GB

The existing prisma image is ~880MB.

@danschmidt5189 danschmidt5189 force-pushed the AP-464-prisma_integration_refactoring branch from 17fac42 to b2b052c Compare October 3, 2025 00:16
@danschmidt5189 danschmidt5189 force-pushed the AP-464-prisma_integration_refactoring branch from 97bace6 to f4dfea5 Compare October 3, 2025 13:59
Copy link
Member

@awilfox awilfox left a comment

Choose a reason for hiding this comment

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

Adding 360M to the resultant image seems like a huge loss when we are already trying to make the image smaller (and I've been doing some work to remove about 300M from it) so that the GitHub Actions cache can actually work.

It also adds a lot of maintenance overhead and security considerations (Node's LTS branches, NPM packages, etc) for no real gain over just including the static SQL. Upstream seems averse to changing their data layer even in minor ways that would give them significant gains, so I don't foresee future migrations beyond the one we have. If they do begin using migrations, we should re-evaluate then.

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.

2 participants