-
Notifications
You must be signed in to change notification settings - Fork 35
fix: local docker updates and type fixes #4827
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
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for bloom-public-seeds ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for partners-bloom-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for bloom-exygy-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
c9faefb
to
8013aa0
Compare
8013aa0
to
3895511
Compare
✅ Deploy Preview for bloom-lakeview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
1d887af
to
fb65067
Compare
fb65067
to
eb25d4c
Compare
2120715
to
2d01228
Compare
@@ -1,29 +1,74 @@ | |||
import { randomUUID } from 'node:crypto'; |
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.
nitpick: everywhere else we import, it's just from 'crypto'
Does this docker setup all for the docker files to pickup live development changes? |
Address #4698 specifically #4998
Description
This PR adds the ability to run Bloom Housing via docker with docker compose. While setting this up, I updated the prisma version, which allowed me to encounter two bugs that were earlier surfaced by a JTC fellow: a type errors in api/src/services/auth.service.ts and api/src/utilities/model-fields.ts.
How Can This Be Tested/Reviewed?
Instructions for using this docker locally can be found in
docker.md
This was only tested on my computer which is an M2 mac. Follow the instructions in
docker.md
to run both just the postgres instance and all applications.For people that run into the same mac issues I had take note of the env variable changes required:
DATABASE_URL=postgresql://postgres:prisma@docker.for.mac.host.internal:5433/bloom_prisma
in the api .env fileBACKEND_API_BASE=http://docker.for.mac.host.internal:3100
in the public and partners .env filesAuthor Checklist:
yarn generate:client
and/or created a migration when requiredReview Process: