Zotonic relies on inotify or fswatch to provide automatic code recompilation.
This works fine for our /opt/zotonic directory: $ apt-get install inotify-tools and restart Zotonic.
But it doesn’t work for /vagrant/sites|modules because /vagrant is mounted through NFS.
Idea: configure a save-hook in our IDEs (PHPStorm to begin with) and trigger a new Zotonic API service call that recompiles the changed file. The file will end up in /opt/zotonic/ebin and from there the Zotonic filewatcher will pick up to hotload the compiled .beam file and/or restart or flush the site if observers/templates are added.
ddeboer
commented
8 years ago
In gitlab by david on Nov 30, 2015, 09:44
Zotonic relies on inotify or fswatch to provide automatic code recompilation.
/opt/zotonicdirectory:$ apt-get install inotify-toolsand restart Zotonic./vagrant/sites|modulesbecause/vagrantis mounted through NFS.Idea: configure a save-hook in our IDEs (PHPStorm to begin with) and trigger a new Zotonic API service call that recompiles the changed file. The file will end up in
/opt/zotonic/ebinand from there the Zotonic filewatcher will pick up to hotload the compiled.beamfile and/or restart or flush the site if observers/templates are added.