Open
Description
The guard-nanoc
way of auto-recompiling a Nanoc site has some drawbacks:
-
Needs configuration:
guard-nanoc
needs aGuardfile
whose configuration is the same pretty much all the time: watchnanoc.yaml
/config.yaml
,Rules
, andcontent
+layouts
+lib
. This configuration is redundant. -
Breaks easily: Because
guard-nanoc
is a separate project that uses internal APIs of Nanoc, it tends to break after a Nanoc release. -
Filesystem only: guard-nanoc can only listen to changes on the local file system.
A nanoc live
command could solve these problems. In order for a nanoc live
command to be full-fledged, it needs the following:
- watcher
- web server
- notifications
- autoreload
- support for Windows (i.e. no
fork
)
Future work includes analysing incoming changes and bypassing the outdatedness checker when possible.