Virtualenv in Dockerfile breaks build_messages about shuup HOT 3 CLOSED

A third option would be to remove the Dockerfile. The current file is not functional, which gives a bad first impression to the docker-inclined folks out there (that includes me). If this option is not chosen, I would like to add a travis task to verify the Dockerfile can actually be built.

from shuup.

Yeah I think the problematic thing here is the npm build. Even if it went through, the build will take some time and it also seems to get stuck pretty easily.

As a fourth option I would suggest to build the image from latest release wheel. That would make things fast and more reliable.

I am happy to accept this change to the Dockerfile. Also with good reasoning I can accept other solutions too, I don't see any need for the virtualenv so maybe the option 1 could be ok.

In case you are not interested to continue with this we will probably do the wheel change later, but for now fixing this is not highest priority for us.

from shuup.

+1

from shuup.