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

Add ability to cache via redis or memcache #34

Open
patcon opened this issue Aug 8, 2016 · 2 comments
Open

Add ability to cache via redis or memcache #34

patcon opened this issue Aug 8, 2016 · 2 comments

Comments

@patcon
Copy link

patcon commented Aug 8, 2016

Any preference? My pupa scraper is running on heroku, so filesystem-based caches are non-ideal :)

Would you accept a PR for one of these options?

@jamesturk
Copy link
Owner

if you're running in production it might be best to disable as you likely
won't use the cache as it isn't intended for actual HTTP caching but
development. but if you want it, either is fine by me! much appreciated

On Aug 8, 2016 6:10 PM, "Patrick Connolly" notifications@github.com wrote:

Any preference? My pupa scraper is running on heroku, so filesystem-based
caches are non-ideal :)

Would you accept a PR for one of these options?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#34, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAfYvMc90WBO_1rqcQNBmqCVTUgiSDkks5qd6lAgaJpZM4Jfhth
.

@patcon
Copy link
Author

patcon commented Aug 9, 2016

Thanks! I see what you're saying, but the city of toronto started throttling the heck out of my scrapers, so I'm trying to sort out how to not restart each time I figure out the limit ;)

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

No branches or pull requests

2 participants