I'm running a docpad instance, and it has been working just fine. Suddenly, now when I run docpad watch, the server starts alright and there are no error messages, but when I load http://localhost:9778, the site is not available. No errors appear in the console either, or at the command line. Anyone have any ideas about what might be going wrong?
I ran into this recently and was able to get things rolling by adding watchFile to the preferredMethods in the docpad config - like so:
# git diff
--- a/docpad.coffee
+++ b/docpad.coffee
@@ -23,5 +23,6 @@ docpadConfig =
templateData: fetchConfig()
watchOptions:
catchupDelay: 0
+ preferredMethods: ['watchFile','watch']
It's mentioned in the Docpad Troublshooting Hope this helps someone else.
UPDATE: I've now seen this on a co-workers machine and this did not solve the issue. It seems the server is just not responding. Running under debug mode, all looks ok, but when I try to hit it (with curl) I get
Recv failure: Connection reset by peer.
UPDATE2: After a bunch of tries, (reinstalling docpad and restarting things), this same fix seemed to work. What we found was that watch would appear to run but and would see files change, but wasn't actually updating things in the out directory. By adding the watchFile to preferredMethods, things seemed a bit less flaky.
It's weird to because the original config was working for a while (a week of development) with no issues. But today it started being flaky on 2 separate dev environments.
The solution that I have run with here is simply to use docpad run, which I think is the best practice. See this discussion for more information.