I am working on a revamp of the spiderable package, so i wanted to ask the community for a quick feedback about the question in the title.
Currently i am working on:
Replace phantomjs with zombie
Planned are also new settings which can be defined in Meteor.Settings:
- host (name or ip)
- allowed bot patterns
- caching, tmp lifetime
- precaching (reocurring process caches urls by time plan)
A seeded or (if possible) automatic prerun and configurable caching would be two very great features.
What exactly do you mean with “seeded”?
I think I would do something like:
Google opens site - check if tmp file is in cache and not too old - ouput tmp or new content
Why doesn’t you just use your mentioned package, when you miss everything of it? xD
Oh by seeded I mean providing a list of url’s to fetch and cache.
Compared to automatic (through crawling the whole site beginning at /)
oh yeah, thats a cool idea and I see the use case.
Just for the sake of completeness: the new package is out and you can try it out at:
Have anyone been able to use this together with Meteor Up (mup) and meteorhacks:cluster?
I’m having difficulties debugging, don’t get why you have to set a port.
webcomponents.js (Polymer) support