02-16-2014 10:32 PM
When I was using Webworks 1.0, I could refersh Ripple to see my latest changes. I liked this a lot.
I am now trying to move to Webworks 2.0, but I must run "webworks serve" to view my changes in my local browser. Any change I make after that requires me to cancel and restart the local web service.
I know the command states "Static file server running on port...".
So my question is, how can I get a dynamic local web service which refreshed automatically when files are changed.
Solved! Go to Solution.
02-19-2014 02:17 PM
02-19-2014 02:58 PM
If you would like to keep the file server running, open up another terminal window and run "webworks prepare" each time you make changes to files. It's possible to automate that using a file watcher on your OS.
02-19-2014 03:20 PM - edited 02-19-2014 03:21 PM
I will try the XAMPP/WampServer approach first, since if I can make this work, it will be the closest thing to my Ripple workflow.
02-19-2014 03:23 PM
I will try automating "webworks prepare" following each file update as my second option. I will look for a lightweight OS file watcher (dedicated utility or something from ruby or node.js) and see how that goes.