Polipus: distributed and scalable web-crawler framework
Ruby
Latest commit 8917a37 Jul 17, 2015 @taganaka v 0.5.1
Permalink
Failed to load latest commit information.
examples example on how to use overflow management Oct 2, 2014
lib v 0.5.1 Jul 17, 2015
spec Propagate user_data values from redis message to fetched pages. Jul 14, 2015
.document Initial commit to polipus. May 12, 2013
.gitignore Add my_test folder to the ignore list Jun 9, 2013
.rspec this project really needs to use 'documentation' here Dec 26, 2014
.rubocop.yml update rubocop and do some clean up with it Dec 28, 2014
.rubocop_todo.yml rubocop todo file updated Jul 9, 2015
.travis.yml
AUTHORS.md Update AUTHORS.md Jul 9, 2015
CHANGELOG.md v 0.5.1 Jul 17, 2015
Gemfile fix gemspec: use gemfile platform and dont load mongo by default Dec 27, 2014
LICENSE.txt Initial commit to polipus. May 12, 2013
README.md
Rakefile organize spec folder correctly Dec 26, 2014
polipus.gemspec minor code cleanup Jul 9, 2015

README.md

Build Status Coverage Status Code Climate RubyGems

Polipus

A distributed web crawler written in ruby, backed by Redis This project has been presented to the RubyDay2013 http://www.slideshare.net/francescolaurita/roll-your-own-web-crawler-rubyday

Features

  • Easy to use
  • Distributed and scalable
  • It uses a smart/fast and space-efficient probabilistic data structure to determine if an url should be visited or not
  • It doesn't exaust your Redis server
  • Play nicely with MongoDB even if it is not strictly required
  • Easy to write your own page storage strategy
  • Focus crawling made easy
  • Heavily inspired to Anemone https://github.com/chriskite/anemone/

Supported Ruby Interpreters

  • MRI 1.9.x >= 1.9.1
  • MRI 2.0.0
  • MRI 2.1.2
  • JRuby 1.9 mode
  • Rubinius

Survival code example

require "polipus"

Polipus.crawler("rubygems","http://rubygems.org/") do |crawler|
  # In-place page processing
  crawler.on_page_downloaded do |page|
    # A nokogiri object
    puts "Page title: '#{page.doc.css('title').text}' Page url: #{page.url}"
  end
end

Installation

$ gem install polipus

Testing

$ bundle install
$ rake

Contributing to polipus

  • Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet.
  • Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it.
  • Fork the project.
  • Start a feature/bugfix branch.
  • Commit and push until you are happy with your contribution.
  • Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
  • Install Rubocop and make sure it is happy
  • Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.

Copyright

Copyright (c) 2013 Francesco Laurita. See LICENSE.txt for further details.