Closed lcreid closed 8 years ago
https://github.com/jekyll/jekyll/issues/2926 suggests that --force_polling
fixes the problem, at the penalty of a bit of CPU.
It does. You now need to do:
jekyll serve --force_polling --host 0.0.0.0
I need to look into aliases.
It looks like aliases aren't the way, but I could probably do shell functions for each of the servers. They would be non-trivial for a couple of reasons:
The issue of making it easier to start and manage Jekyll and Rails is a little more complicated than I first thought. Closing this because the --force_polling
flag fixes this specific issue.
jekyll serve --incremental --host 0.0.0.0
doesn't see the file changes made on the host, so it's useless.