0
votes

I'm fighting for some time with docpad performance in local development. Have issue with live reload. Small change in some less file takes even 100sec to regenerate and reload the server. It looks like even though there was a change in one file, he regenerates everything. I've added those, as suggested on docpad page:

watchOptions: 
  preferredMethods: ['watchFile','watch']
  catchupDelay: 0 
regenerateDelay: 0

also disabled tag plugin for local dev, as he is pretty nasty with its constant tags regeneration.

I'm on docpad 6.63.8 with the following plugins: coffeescript, eco, gulp, highlightjs, less, livereload, lunr, marked, paged, partials, tags, text

I thought that I will simply get over it with gulp watch, but obviously watch is not enough, server needs to be reloaded anyway and I don't think it is possible to replace livereload plugin with gulp livereload or I'm just to stupid to do this

I'm using text plugin a lot, and maybe it slows down?

I wanted to overcome the issue by using gulp for watching and regeneration and manual restart of the server and docpad server but I noticed that docpad server is regenerating all the files, even though they were already regenerated and are in the out dir.

Any ideas?

1

1 Answers

0
votes

Yep - I've seen this problem with livereload. I see it especially with dynamic pages. To be honest I think the best solution for the moment is to just remove livereload - remove it from the package.json file and delete the livereload node_modules directory. To my mind, livereload is only saving you from having to hit the reload button on the browser.