WWMD was originally intended to provide a console helper tool for conducting web application security assessments (which is something I find myself doing alot of). I've spent alot of time and had alot of success writing application specific fuzzers + scrapers to test with. WWMD provides a base of useful code to help you work with web sites both in IRB and by writing scripts that can be as generic or as application specific as you choose. There's alot of helpful stuff crammed in here and its usage has evolved alot. It's not intended to replace, remove or be better than any of the tools you currently use. In fact, WWMD works best *with* the tools you currently use to get stuff done. You get convenience methods for getting, scraping, spidering, decoding, decrypting and munging user inputs, pages and web applications. It doesn't try to be smart. That's up to you. What's here is the basic framework for getting started. There's a raft of cookbook scripts and examples that are coming soon so make sure you check the wiki regularly.

Wikipedia-API is a ruby wrapper for the MediaWiki API

= Ungulate According to Wikipedia, this can mean "hoofed animal". Camels have hooves. This is a gem for uploading and processing images using an Amazon Web Services stack. It comes with a few goodies: * ungulate_server.rb - simple queue runner that expects a YAML-encoded job description for RMagick * Ungulate::FileUpload - a model for e.g. Rails that does some cryptography stuff - example to follow * A view helper for Rails: "ungulate_upload_form_for" == Installation gem install ungulate == Documentation http://wiki.github.com/camelpunch/ungulate/ == Note on Patches/Pull Requests * Fork the project. * Make your feature addition or bug fix. * Add tests for it. This is important so I don't break it in a future version unintentionally. * Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull) * Send me a pull request. Bonus points for topic branches. == Copyright Copyright (c) 2011 Camel Punch Limited. See LICENSE for details.

a sinatra/couchdb wiki

Wikipedia-API is a ruby wrapper for the MediaWiki API

Ruby client for Wikidata

This plugin adds a wiki macro to make it easier to list the details of issues on a wiki page.

a simple wiki powered by sinatra

get article text from wikipedia from cli

Provides a nginx mod_zip compatible file manifest for streaming support. See http://wiki.nginx.org/NginxNgxZip for the nginx module.

This is a packaged gem version of the CSV import/export tasks on the {i18n-tasks Wiki}[https://github.com/glebm/i18n-tasks/wiki/Custom-CSV-import-and-export-tasks]. :include: Contributing.rdoc :include: Licence.rdoc

Unofficial Chef Server scripts and related stuff. http://wiki.opscode.com/display/chef

A little parser for Wikipedia's 'In the News' content

WhatIs.this fetches any entity metadata from Wikipedia by title and renders it concisely and informatively. Think `WhatIs.these(list, of, user, entered, toponyms).map(&:coordinates)` for example.

== OceanDynamo As one important use case for OceanDynamo is to facilitate the conversion of SQL databases to no-SQL DynamoDB databases, it is important that the syntax and semantics of OceanDynamo are as close as possible to those of ActiveRecord. This includes callbacks, exceptions and method chaining semantics. OceanDynamo follows this pattern closely and is of course based on ActiveModel. The attribute and persistence layer of OceanDynamo is modeled on that of ActiveRecord: there's +save+, +save!+, +create+, +update+, +update!+, +update_attributes+, +find_each+, +destroy_all+, +delete_all+, +read_attribute+, +write_attribute+ and all the other methods you're used to. The design goal is always to implement as much of the ActiveRecord interface as possible, without compromising scalability. This makes the task of switching from SQL to no-SQL much easier. OceanDynamo uses only primary indices to retrieve related table items and collections, which means it will scale without limits. OceanDynamo is fully usable as an ActiveModel and can be used by Rails controllers. Thanks to its structural similarity to ActiveRecord, OceanDynamo works with FactoryBot. See also Ocean, a Rails framework for creating highly scalable SOAs in the cloud, in which ocean-dynamo is used as a central component: http://wiki.oceanframework.net

Facebooker is a Ruby wrapper over the Facebook[http://facebook.com] {REST API}[http://wiki.developers.facebook.com/index.php/API]. Its goals are: * Idiomatic Ruby * No dependencies outside of the Ruby standard library (This is true with Rails 2.1. Previous Rails versions require the JSON gem) * Concrete classes and methods modeling the Facebook data, so it's easy for a Rubyist to understand what's available * Well tested

A wiki engine in Rails 5.

Display Wiki channel in navbar for wike pages.

It is a command line tool to register your resources in Wiki page (Markdown format).

Display Wiki channel in navbar for wike pages.