Warp – self-contained, single binary applications

Re:Warp – self-contained, single binary applications by weberc2 on Friday October 12, 2018 @07:42PM (#18205468)

Thanks for the suggestions! I had to check, but we do both of those things. To make sure that node_modules aren't overwritten, we mount an empty named volume to the node_modules directory. I guess mounting the named volume directory somehow causes the node_modules directory from the base image to appear inside of the bind-mounted directory. We do the same thing for venvs as well.

We use venvs inside of the Docker container because we use pipenv and apparently pipenv's support for installing to the system is buggy and/or idiosyncratic.

[ Parent | on HN ]

Re:Warp – self-contained, single binary applications by TheDong on Friday October 12, 2018 @09:51PM (#18205935)

Named volumes are hacky to no end and you shouldn't be using them to make sure it's empty; you should be using `.dockerignore` or being careful about what you copy in.

The pipenv bit is probably more reasonable, and I'm afraid I haven't used it enough to be sure what rough edges are likely there.

[ Parent | on HN ]