-
Notifications
You must be signed in to change notification settings - Fork 35
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
[Bug]: Docker container vue-spree-frontend-1 fails to find rifraf command #239
Comments
same issue |
Fixed it by adding
And
Not sure it is the right way to do it though. |
Hi @Con607 - interesting issue, we haven't run into it before. Technically rimraf is included in package.json so it should be installed already. Let me try to reproduce it on a clean install. |
@rafalcymerys I can confirm this happens on a freshly cloned git repo. @Con607's workaround works insofar as getting the application running |
The Dockerfile's both run |
The issue is still valid. |
I saw in logs error with husky, it wants to list .git folder. Workaround : remove .git from .dockerignore file now bin/start-docker in run-able |
Interesting. What if you just create a dummy .git directory as a part of the Dockerfile? It may be slightly better than including the full repo in the container image |
Expected Behavior
I'd expect the instructions to use the dockerized setup to run both the backend and the frontend explained at https://github.com/vuestorefront/spree#running-vue-storefront--spree-in-docker to work
Actual Behavior
bin/setup
andbin/seed
work as expectedbin/start
there is a problem** the docker-compose for the spree backend starts and runs (I can access http://localhost:4000/).
Possible Solution
No response
Steps to reproduce
What version of Spree integration are you using?
d1c7335
What version of Node.js are you using?
14.15 (defined by Dockerfile.development)
What browser (and version) are you using?
Firefox, but doesn't matter
What operating system (and version) are you using?
Debian 11
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: