Closed a-magdy closed 6 years ago
Unless I'm misunderstanding, npm start
will fail on windows.
npm start
test results:
Ooops, I didn't consider windows!
.. well I could remove the start
script from package.json
to avoid confusion, and leave start.sh
to be executed in docker-compose, would that be an acceptable solution?
@a-magdy I personally see no reason to have the start.sh in the project.
On the other hand I find the new docker-compose very useful. Tested on Ubuntu 16.04 LTS and works fine - witter service looks properly configured, the volume is properly mapped, the watcher is working just fine picking up the file changes...
My two cents
git reset --hard
and git checkout branch
and if someone generates his own package-lock.json (some people change package versions inside package.json to make the code work on their environment) switching between branches can be tricky for some Thanks @s-slavchev for your comment :)
there is no need for start.sh
.start.sh
so it would be hidden by default, and users won't have to worry about it!package-lock.json will be trouble for many students
@s-slavchev @jakearchibald I updated the code to avoid any conflicts, and the changes so far are:
docker-compose.yml
command to be inlineREADME.md
ports configuration using docker-compose section & added a troubleshooting node-sass linestart
script from package.jsonstart.sh
scriptpackage-lock.json
@a-magdy thanks for this! Can you move the local-machine instructions above the docker ones? Generally I'd rather they tried that first. Cheers!
@jakearchibald Done :)
Merged, thank you!
docker-compose
, by sending the source code as a volume, to ease developing using docker.Addstart
script in package.json, adding a script that install npm modules if not found.Addpackage-lock.json
file