./localdev.js run zen watches for changes in dust files, and restarts the cp-zen-platform processes to make the new changes be picked up. Despite this, you sometimes get the new template, sometimes get the old one.
I think this may have something to do with the fact that multiple processes (one for each thread/core) for each service, and perhaps only one gets restarted.
The ideal scenario is to disabled dustjs's caching and get rid of the file watcher.
./localdev.js run zen
watches for changes in dust files, and restarts the cp-zen-platform processes to make the new changes be picked up. Despite this, you sometimes get the new template, sometimes get the old one.I think this may have something to do with the fact that multiple processes (one for each thread/core) for each service, and perhaps only one gets restarted.
The ideal scenario is to disabled dustjs's caching and get rid of the file watcher.