Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Built-in live command #24

Open
3 of 5 tasks
denisdefreyne opened this issue Oct 23, 2017 · 0 comments
Open
3 of 5 tasks

Built-in live command #24

denisdefreyne opened this issue Oct 23, 2017 · 0 comments
Labels

Comments

@denisdefreyne
Copy link
Member

denisdefreyne commented Oct 23, 2017

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant