Difficult to figure out docker-compose

[Sid Sahai]

I'm trying to run this project via docker-compose but I get some errors that I generally don't see in python libraries:

• why do we need to include the entire source code in a separate parallel folder outside our project? Why can't we add mercury to our own existing docker-compose/Dockerfile via the regular requirements.txt? It is quite difficult to modify all services etc of a large project, just for one library - it is too opinionated (we don't use nginx nor postgres).

• I get permission errors because it seems mercury tries to write files inside the /usr/src/python3.10/libraries/mercury folder. My docker user does not have write permissions across the entire image - I can't use root user here for security reasons. I also have a different base image.

Please solve these issues if possible and make it more suitable for production, I think mercury is a really helpful project overall!

[Piotr]

Hi @sidthekidder,

Thanks for opening the issue. You can try to simply run mercury command in docker if you would like simple setup. Anyway, we will try to address your issues.