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
resource-recorder: update the docker compose file #1092
resource-recorder: update the docker compose file #1092
Conversation
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.
I think we can use the same minimal prepare.sh
file as gateway and auth 😄
c7ddd5a
to
ade7e07
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.
Just have to undo comments
ade7e07
to
b348a09
Compare
...of the custom directory from the examples to custom-serivce. This made our init for `None` example fail.
8a33c78
to
e4bf12f
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.
PR just has an unexpected change
* resource-recorder: added docker compose service * resource-recorder: added prepare.sh * docker-compose: fix provisioner/resource-recorder deps * docker-compose: fixed resource-recorder args * review/resource-recorder: addressed P review and fixed db_path * cargo-shuttle: custom resources changed the name... ...of the custom directory from the examples to custom-serivce. This made our init for `None` example fail.
Description of change
Added a docker-compose service for resource-recorder and
Makefile
tag env variable.How has this been tested? (if applicable)
Started Shuttle locally and it worked. Tested on unstable too.