Closed dillfrescott closed 1 year ago
Have you already initialized the services with bin/init
?
Ah, yes, and I even tried it multiple times thinking maybe it left something incomplete.
Would you mind sharing your full logs? You can obtain them by executing $ docker-compose logs --timestamps
once the offending containers have exited.
I am sorry I was using a vps to run the project so I terminated the vps because I had to pay for it. I can try to run it again sometime and send you the logs...
Have you tried to install both mutagen and mutagen-compose? Mutagen-compose needs a matching version of Mutagen installed and available in your path.
Yes, they were both installed and on the system path
What vps did you use?
Also you should try it first on local machine as I had tried it and had no problems. The point of using docker compose is to have consistent env across devices so I really dont understand the missing webpack
part.
I used one from serverspace.us
. I've kinda moved on from this project anyways.
Closing until this issue can either be reproduced or logged
reproduced this again on a local machine. same issue
some say: