-
Notifications
You must be signed in to change notification settings - Fork 6
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
ENG-376 docker compose setup for running GitCloud #21
base: main
Are you sure you want to change the base?
Conversation
@vkarpov15 is attempting to deploy a commit to the osohq Team on Vercel. A member of the Team first needs to authorize it. |
@samscott89 @gj @gsarjeant tagging because I'm not allowed to add reviewers to this PR. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@vkarpov15 I had to modify the base images for the I don't have permission to push the branch to your repo to submit a PR there, but it's a small change. Sorry for the long delay getting to this. |
Here are the stack traces I got that led to this, for reference:
|
I found this issue against psycopg that indicates ongoing issues with python 3.13, so I downgraded the jobs service to 3.12. I bumped gitcloud to the latest node LTS just as an experiment, but that fixed the SQLite error. |
Added Dockerfiles for
services/jobs
,frontend
, and Oso local binary. And added a docker-compose that can run gitcloud, jobs, frontend, Oso local binary, and postgres. I wasn't able to figure out how to reliably seed the db without making some substantial changes, so I just added a separate seed script to theservices/gitclub
Makefile with instructions to only run that seed script once.