-
Notifications
You must be signed in to change notification settings - Fork 2
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
problem with cloud build #1
Comments
Hi, Could you pls be more specific about how to reproduce this --- I did not look into the src, and for now, I don't understand the surrounding architecture. Thx |
btw this should not be required: await db.ready(); If it changed something there is a bug in the core. |
and could we have at least a monade to pass in the db instead of globally declaring? This is more of a bit of code hygiene |
@jchris clear your ~/.fireproof and try again. |
That sounds like a sledgehammer solution. |
It is, but in my case it was keyid mismatch and wanted to see the app error. I haven't dug deeper, but with cloud gateway enabled, keybag is in its own dist folder (kb-dir-FireproofCloud) for each invocation but data is centralized in ~/.fireproof? |
That should not be the case --- I did not configure that in that way. Should we have a look at it together? |
It took me a day to figure out my local fireproof development workflow. Here are some modifications I made to I suppressed the "extractKey" warning in In jimpick/connect@cd9e0ec#diff-122bda192034b3469ed452a2e55213c140de3003defc3d0245d47b5686f363d2L107 In the same commit, I also changed the "keybag" location to be When I run it, I first do |
For some reason the cloud build give an error
The text was updated successfully, but these errors were encountered: