-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
ask-the-documents
: Deploy to Fly
#3251
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
Conversation
3950ceb
to
f01771d
Compare
This stack of pull requests is managed by Graphite. Learn more about stacking. |
ask-the-documents
: Deploy to Fly
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.
We should update the README to be clear how to test this app locally with a pgvector enabled DB.
0d7e6e7
to
bd81e2d
Compare
f01771d
to
b057248
Compare
b057248
to
6e7c183
Compare
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.
Great stuff
ask-the-documents
example app in the Wasp monorepo #3141Did the inital deploy to Fly.io, and adds it to the CI release deploy.
https://ask-the-documents-client.fly.dev/
The custom image with pgvector is handled by pushing a custom image to
ghcr.io/wasp-lang/ask-the-documents-fly-db
, instead of using the very custom DB image. This is inline with our custom image recommendations for Fly.PR hierarchy:
ask-the-documents
: Import app into repo #3174 just imports the repo and runs prettier on itask-the-documents
: Add dotenv files #3252 adds dotenv files with the config that was on railwayask-the-documents
: Deploy to Fly #3251 (👈 this one) adds deployment to Fly in CIask-the-documents
: Add CI testing #3250 adds simple e2e testing to CI