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
The guard-nanoc way of auto-recompiling a Nanoc site has some drawbacks:
Needs configuration: guard-nanoc needs a Guardfile whose configuration is the same pretty much all the time: watch nanoc.yaml/config.yaml, Rules, and content+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.
The text was updated successfully, but these errors were encountered:
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 ananoc live
command to be full-fledged, it needs the following:fork
)Future work includes analysing incoming changes and bypassing the outdatedness checker when possible.
The text was updated successfully, but these errors were encountered: