being able to test the SAT solver components interacting with the provided container infrastructure locally would allow quicker development and debugging issues.
It would be great if consumers of this infrastructure could provide local formulas (e.g. via a directory mounted into the container), that would be forwarded to the solver by the default entry point, instead of talking to AWS resources. A possible way to implement would to support environment variables in the infrastructure code to switch from listening on SQS and using S3, and instead read the file from a (container) local directory, which was mounted in the docker run call. Then, a corresponding docker run example command line would help users to start integrating without setting up all AWS infrastructure. Furthermore, the AWS infrastructure does not have to be refreshed with all modifications to the local images that should be tested. Thanks!
Dear all,
being able to test the SAT solver components interacting with the provided container infrastructure locally would allow quicker development and debugging issues.
It would be great if consumers of this infrastructure could provide local formulas (e.g. via a directory mounted into the container), that would be forwarded to the solver by the default entry point, instead of talking to AWS resources. A possible way to implement would to support environment variables in the infrastructure code to switch from listening on SQS and using S3, and instead read the file from a (container) local directory, which was mounted in the
docker run
call. Then, a correspondingdocker run
example command line would help users to start integrating without setting up all AWS infrastructure. Furthermore, the AWS infrastructure does not have to be refreshed with all modifications to the local images that should be tested. Thanks!Best, Norbert