You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently using vagrant to control the dev environment. The work-flow is roughly:
vagrant up
vagrant ssh
# In the vagrant shell:cd /vagrant
export NODE_ENV='development'&& npm run build-server && npm run server
which is not exactly sexy and easy.
Besides, when developing we manually recompile and restart the dev server and we often end-up starting other services like mongo-express or node-inspector.
All this could be simplified a lot. Compare it to the client work-flow which is:
npm start # only once...
If someone is motivated, a good step could be to have the server automatically started after:
vagrant up # Run mongo-express, build the server and start it
Bonus: Offer an option to have a watch mode like in the client where the server is automatically rebuild and restarted when a server file change.
The text was updated successfully, but these errors were encountered:
We are currently using vagrant to control the dev environment. The work-flow is roughly:
which is not exactly sexy and easy.
Besides, when developing we manually recompile and restart the dev server and we often end-up starting other services like
mongo-express
ornode-inspector
.All this could be simplified a lot. Compare it to the client work-flow which is:
npm start # only once...
If someone is motivated, a good step could be to have the server automatically started after:
vagrant up # Run mongo-express, build the server and start it
Bonus: Offer an option to have a watch mode like in the client where the server is automatically rebuild and restarted when a server file change.
The text was updated successfully, but these errors were encountered: