= PostgreSQL ActiveRecord Extensions

What we've got here is a collection of extensions to the ActiveRecord
PostgreSQL adapter including:

* support for constraints in migrations including CHECK constraints, foreign
  keys, unique constraints and so forth. Constraints can be added per column
  and per table.

* some methods for manipulating all sorts of stuff like procedural languages,
  functions, sequences, views, schemas and triggers.

* better support for creating indexes with expressions so you can use functions
  and GiST and GIN indexes.

* support for manipulating role privileges.

* support for some PostgreSQL-specific statements like INHERITS and LIKE when
  creating tables.

* support for automatically detecting foreign key relationships and building
  ActiveRecord associations accordingly. This associations can be overridden
  as necessary and are sane enough that they won't try to overwrite existing
  associations.

* support for some PostGIS functionality including some support for using
  PostGIS columns in migrations. For manipulating PostGIS data, see our
  geos-extensions gem at https://github.com/zoocasa/geos-extensions or
  the RGeo project at https://github.com/dazuma/rgeo .

Add a note about creating db/development_schema.sql.

= PostgreSQL ActiveRecord Extensions

What we've got here is a collection of extensions to the ActiveRecord
PostgreSQL adapter including:

* support for constraints in migrations including CHECK constraints, foreign
  keys, unique constraints and so forth. Constraints can be added per column
  and per table.

* some methods for manipulating all sorts of stuff like procedural languages,
  functions, sequences, views, schemas and triggers.

* better support for creating indexes with expressions so you can use functions
  and GiST and GIN indexes.

* support for manipulating role privileges.

* support for some PostgreSQL-specific statements like INHERITS and LIKE when
  creating tables.

* support for automatically detecting foreign key relationships and building
  ActiveRecord associations accordingly. This associations can be overridden
  as necessary and are sane enough that they won't try to overwrite existing
  associations.

* support for some PostGIS functionality including some support for using
  PostGIS columns in migrations. For manipulating PostGIS data, see our
  geos-extensions gem at https://github.com/zoocasa/geos-extensions or
  the RGeo project at https://github.com/dazuma/rgeo .

== Building db/schema.rb

While this extension has support for creating a bunch of PostgreSQL-specific
DDL statements, it can't actually reverse the process yet to create the Ruby
equivalent code in your schema.rb file. To create a suitable schema file
that you can use for creating test databases or just to view the schema
itself, you can try switching the ActiveRecord configuration option for
schema_format from :ruby to :sql like so:

  config.active_record.schema_format = :sql

This will tell ActiveRecord to use the pg_dump utility to create a file
containing the database schema in db/development_structure.sql.

Details on this configuration option can be found here:

http://guides.rubyonrails.org/configuring.html


= Stripe Python bindings

{<img src="https://travis-ci.org/stripe/stripe-python.svg?branch=master" alt="Build Status" />}[https://travis-ci.org/stripe/stripe-python]

== Installation

You don't need this source code unless you want to modify the
package. If you just want to use the Stripe Python bindings, you
should run:

  pip install --index-url https://code.stripe.com --upgrade stripe

or

  easy_install --index-url https://code.stripe.com --upgrade stripe

See http://www.pip-installer.org/en/latest/index.html for instructions
on installing pip. If you are on a system with easy_install but not
pip, you can use easy_install instead. If you're not using virtualenv,
you may have to prefix those commands with +sudo+. You can learn more
about virtualenv at http://www.virtualenv.org/

To install from source, run:

  python setup.py install

== Documentation

Please see https://stripe.com/docs/api for the most up-to-date
documentation.

Move the badge inline with the header


= Changelog

Per-release changes to Handler.

== 0.8.0 (2009 Oct 12)

First release.

Fix changelog (was boilerplate copied from Handler gem).

= Changelog

Per-release changes to GoogleCustomSearch.

== 0.3.0 (2009 Oct 14)

First release.


== Pull Request 20015-08-06

Changes implemented per vimeo's updated api:

* [Endpoint](https://developer.vimeo.com/apis/oembed#endpoint)
* [base_uri](https://developer.vimeo.com/apis/oembed#json-example)
* [info parameters](https://developer.vimeo.com/apis/oembed#json-example)

== 1.0.0, released 2009-09-28

* Upgraded to v2 of the API.
* Added some upload helpers.
* Huge refactor for the Advanced API making it easier to add/modify method calls.

== 0.2.2, released 2009-04-21

* Removed CGI escapes. Vimeo should be handling them on their end.

== 0.2.1, released 2009-01-06

* Last version was missing files.

== 0.2.0, released 2009-01-06

* Major re-factor of each request method.
* Separated the simple and advanced APIs into their own modules.
* Added some documentation.
* Updated the README.

== 0.1.2, released 2008-10-26

* Initial release

Embed links using rdoc syntax

== Pull Request 20015-08-06

Changes implemented per vimeo's updated api:

* {Endpoint}{https://developer.vimeo.com/apis/oembed#endpoint}
* {base_uri}{https://developer.vimeo.com/apis/oembed#json-example}
* {info parameters}{https://developer.vimeo.com/apis/oembed#json-example}

== 1.0.0, released 2009-09-28

* Upgraded to v2 of the API.
* Added some upload helpers.
* Huge refactor for the Advanced API making it easier to add/modify method calls.

== 0.2.2, released 2009-04-21

* Removed CGI escapes. Vimeo should be handling them on their end.

== 0.2.1, released 2009-01-06

* Last version was missing files.

== 0.2.0, released 2009-01-06

* Major re-factor of each request method.
* Separated the simple and advanced APIs into their own modules.
* Added some documentation.
* Updated the README.

== 0.1.2, released 2008-10-26

* Initial release


= net-http-not_modified_cache - {<img src="https://travis-ci.org/einstein/net-http-not_modified_cache.png" />}[http://travis-ci.org/einstein/net-http-not_modified_cache]

Description

== Installation

  gem install net-http-not_modified_cache

== Usage

Instructions

Use secure.travis-ci.org when referencing build status images with https

= net-http-not_modified_cache - {<img src="https://secure.travis-ci.org/einstein/net-http-not_modified_cache.png" />}[http://travis-ci.org/einstein/net-http-not_modified_cache]

Description

== Installation

  gem install net-http-not_modified_cache

== Usage

Instructions


== Sensu Admin

Sensu-admin is a web application to interface with the sensu-api, it displays
events and clients and can silence events etc.

== Getting Started

rake db:migrate
rake db:seed

Make sure your post-deploy task runs "whenever --update-crontab from the rails cwd"

The seed file creates a user account named admin@example.com with a password of secret.

== TODO
* Settings for api, rabbitmq, etc
* RabbitMQ dashboard, health of everything
* permission
* add/remove users
* Log Downtime schedule, execution, and completion
* Make a downtime info page
* popover in events looks like crap on small or huge screens
* Use sensu config for production sensu-admin -- https://github.com/sensu/sensu/blob/master/lib/sensu/settings.rb
* Make a note when silencing or creating a downtime that event handlers must use sensu-plugin or hit the API to check for silencing
* Do not render out all modals into the html, do like you do with the main modal on events and render via ajax

Implement jquery mobile support... eventually.

== Sensu Admin

Sensu-admin is a web application to interface with the sensu-api, it displays
events and clients and can silence events etc.

== Getting Started

rake db:migrate
rake db:seed

Make sure your post-deploy task runs "whenever --update-crontab from the rails cwd"

The seed file creates a user account named admin@example.com with a password of secret.

== TODO
* Settings for api, rabbitmq, etc
* RabbitMQ dashboard, health of everything
* permission
* add/remove users
* Log Downtime schedule, execution, and completion
* Make a downtime info page
* popover in events looks like crap on small or huge screens
* Use sensu config for production sensu-admin -- https://github.com/sensu/sensu/blob/master/lib/sensu/settings.rb
* Make a note when silencing or creating a downtime that event handlers must use sensu-plugin or hit the API to check for silencing
* Do not render out all modals into the html, do like you do with the main modal on events and render via ajax
* Full jquery mobile support


= DESCRIPTION:
Installs Zookeeper

= REQUIREMENTS:
* Java cookbook version >= 1.5

= ATTRIBUTES:

= USAGE:

Add runit as a dependency for zookeeper

= DESCRIPTION:
Installs Zookeeper

= REQUIREMENTS:
* Java cookbook version >= 1.5
* Runit cookbook

= ATTRIBUTES:

= USAGE:


= SolandraObject

SolandraObject merges the functionality of Gotime's CassandraObject and Sunspot::Rails.
It does this by automatically indexing attributes declared as part of the model

=== Installation

Add the following to your Gemfile:

  gem 'thrift', '~> 0.7.0'
  gem 'cassandra', '~> 0.12.1'
  gem 'solandra_object', '~> 0.0.1'

Change version numbers as appropriate.

Of course you need a solr/solandra instance running to use this.
They also need to be properly configured. Create a default config file
for sunspot_rails like this:

  rails generate sunspot_rails:install

Then edit config/sunspot.yml appropriately. You might need to set the
path option for solr like

  path: /solandra

when using Solandra (you will get 404 errors if this setting is incorrect).

=== Example

  class Category < SolandraObject::Base
    key :uuid
    string :name
    string :description
    array :sub_categories, :unique => true
    json :extra_attributes
  end

For more examples and instructions on how to use this, consult the documentation
for sunspot, sunspot_rails, cassandra_object and solandra.

Update example on using create_solr rake task

= SolandraObject

SolandraObject merges the functionality of Gotime's CassandraObject and Sunspot::Rails.
It does this by automatically indexing attributes declared as part of the model

=== Installation

Add the following to your Gemfile:

  gem 'thrift', '~> 0.7.0'
  gem 'cassandra', '~> 0.12.1'
  gem 'solandra_object', '~> 0.0.1'

Change version numbers as appropriate.

Of course you need a solr/solandra instance running to use this.
They also need to be properly configured. Create a default config file
for sunspot_rails like this:

  rails generate sunspot_rails:install

Then edit config/sunspot.yml appropriately. You might need to set the
path option for solr like

  path: /solandra

when using Solandra (you will get 404 errors if this setting is incorrect).

Configure solandra with the SolandraObject schema:

  rake so:create_solr
  rake so:create_solr RAILS_ENV=test

=== Example

  class Category < SolandraObject::Base
    key :uuid
    string :name
    string :description
    array :sub_categories, :unique => true
    json :extra_attributes
  end

For more examples and instructions on how to use this, consult the documentation
for sunspot, sunspot_rails, cassandra_object and solandra.


== README

This README would normally document whatever steps are necessary to get the
application up and running.

Things you may want to cover:

* Ruby version

* System dependencies

* Configuration

* Database creation

* Database initialization

* How to run the test suite

* Services (job queues, cache servers, search engines, etc.)

* Deployment instructions

* ...

Please feel free to use a different markup language if you do not plan to run
<tt>rake doc:app</tt>.

Update readme (from other branch)

# Rap Analysis WebApp

## Summary

This app allows people to input a transcription of a rap song (words, rhythm, rhyme, and rhythm of stressed syllables), and have the song displayed in a way that illustrates the musicality of the song. After transcription, the app will supply some statistics about the song, and can do so about artists and albums as a whole.

I created this app part of the way through Dev Bootcamp as a passion project. I used Sinatra as the framework because I did not yet know Rails.

## Moving Forward

Before I move forward with this app, I need to decide what languages and frameworks I am going to use. I am considering using JavaScript frontend such as React (seeing as the main feature of the site is a single page for transcribing songs). I am also considering using Python backend because I would eventually like to incorporate machine learning.

Aside from the intimidating task of choosing new technologies (and recreating the app ground up), my next steps would be to change the way a user inputs a new song to more forgiving and intuitive. Any CSS whatsoever would also be an improvement on the barebones site.

The master branch of this is deployed on Heroku at: http://gentle-wildwood-3897.herokuapp.com

If you have any questions or comments, feel free to shoot me an email at mark.janzer@gmail.com


Yet another FizzBuzz in Ruby. Provides simple and fast solution
to a popular FizzBuzz problem for Ruby.

[![Build Status](https://secure.travis-ci.org/kwilczynski/fizzbuzz.png?branch=master)](http://travis-ci.org/kwilczynski/fizzbuzz)

Update Travis CI status image URL to work with RDoc.

Yet another FizzBuzz in Ruby. Provides simple and fast solution
to a popular FizzBuzz problem for Ruby.

{<img src="https://travis-ci.org/kwilczynski/fizzbuzz.png?branch=master"/>}[https://travis-ci.org/kwilczynski/fizzbuzz]


= Rack::Test

- Code: http://github.com/brynary/rack-test

== Description

Rack::Test is a small, simple testing API for Rack apps. It can be used on its
own or as a reusable starting point for Web frameworks and testing libraries
to build on. Most of its initial functionality is an extraction of Merb 1.0's
request helpers feature.

== Features

* Maintains a cookie jar across requests
* Easily follow redirects when desired
* Set request headers to be used by all subsequent requests
* Small footprint. Approximately 200 LOC

== Example

  require "rack/test"

  class HomepageTest < Test::Unit::TestCase
    include Rack::Test::Methods

    def app
      MyApp.new
    end

    def test_redirect_logged_in_users_to_dashboard
      authorize "bryan", "secret"
      get "/"
      follow_redirect!

      assert_equal "http://example.org/redirected", last_request.url
      assert last_response.ok?
    end

  end

== Install

To install the latest release as a gem:

  sudo gem install rack-test

== Authors

- Maintained by {Bryan Helmkamp}[mailto:bryan@brynary.com]
- Contributions from Simon Rozet and Pat Nakajima
- Much of the original code was extracted from Merb 1.0's request helper

== License

Copyright (c) 2008-2009 Bryan Helmkamp, Engine Yard Inc.
See MIT-LICENSE.txt in this directory.

Add install instructions for Bundler

= Rack::Test

- Code: http://github.com/brynary/rack-test

== Description

Rack::Test is a small, simple testing API for Rack apps. It can be used on its
own or as a reusable starting point for Web frameworks and testing libraries
to build on. Most of its initial functionality is an extraction of Merb 1.0's
request helpers feature.

== Features

* Maintains a cookie jar across requests
* Easily follow redirects when desired
* Set request headers to be used by all subsequent requests
* Small footprint. Approximately 200 LOC

== Example

  require "rack/test"

  class HomepageTest < Test::Unit::TestCase
    include Rack::Test::Methods

    def app
      MyApp.new
    end

    def test_redirect_logged_in_users_to_dashboard
      authorize "bryan", "secret"
      get "/"
      follow_redirect!

      assert_equal "http://example.org/redirected", last_request.url
      assert last_response.ok?
    end

  end

== Install

To install the latest release as a gem:

  sudo gem install rack-test

Or via Bundler:

  gem "rack-test", require: "rack/test"

== Authors

- Maintained by {Bryan Helmkamp}[mailto:bryan@brynary.com]
- Contributions from Simon Rozet and Pat Nakajima
- Much of the original code was extracted from Merb 1.0's request helper

== License

Copyright (c) 2008-2009 Bryan Helmkamp, Engine Yard Inc.
See MIT-LICENSE.txt in this directory.


= jquery-ujs

Unobtrusive jQuery with Rails 3

== Installation

jQuery 1.4, 1.4.1 and 1.4.2 can be used. However because of http://jsbin.com/uboxu3/7/ issue it is
recommended to use jQuery 1.4.1.

=== Step 1

Download jQuery from http://docs.jquery.com/Downloading_jQuery and put the file in public/javascripts - for example, the file might be:

  public/javascripts/jquery-1.4.1.min.js

=== Step 2

Copy rails.js from http://github.com/rails/jquery-ujs/raw/master/src/rails.js into public/javascripts - overwriting the prototype one (you can also delete the other prototype files if you don't need them for anything else.)

=== Step 3 (optional)

Switch the javascript_include_tag :defaults to use jquery instead of the default prototype helpers.

file config/application.rb

  config.action_view.javascript_expansions[:defaults] = %w(jquery rails application)

= Testing

== Installation

  $ gem install bundler
  $ bundle install

== Running tests

  $ bundle exec ruby test/server.rb

Visit http://localhost:4567 and all the tests should pass. If you want to change any settings then change the settings at the top of test/public/test/settings.js

Add instructions for automated installation

= jquery-ujs

Unobtrusive jQuery with Rails 3

== Automated Installation

=== Step 1

Add this line to your Gemfile:

  gem 'jquery-rails'

=== Step 2

Run this command:

  $ rails generate jquery:install # --ui if you want jQuery UI

=== Step 3

There is no step three.

== Manual installation

jQuery 1.4, 1.4.1 and 1.4.2 can be used. However because of http://jsbin.com/uboxu3/7/ issue it is
recommended to use jQuery 1.4.1.

=== Step 1

Download jQuery from http://docs.jquery.com/Downloading_jQuery and put the file in public/javascripts - for example, the file might be:

  public/javascripts/jquery-1.4.1.min.js

=== Step 2

Copy rails.js from http://github.com/rails/jquery-ujs/raw/master/src/rails.js into public/javascripts - overwriting the prototype one (you can also delete the other prototype files if you don't need them for anything else.)

=== Step 3 (optional)

Switch the javascript_include_tag :defaults to use jquery instead of the default prototype helpers.

file config/application.rb

  config.action_view.javascript_expansions[:defaults] = %w(jquery rails application)

= Testing

== Installation

  $ gem install bundler
  $ bundle install

== Running tests

  $ bundle exec ruby test/server.rb

Visit http://localhost:4567 and all the tests should pass. If you want to change any settings then change the settings at the top of test/public/test/settings.js


= ruby-box

Ruby SDK for Box API 2.0

== Contributing to ruby-box

* Rename account.example to account.yml and fill in your Box credentials
* Type bundle install
* Type rake.. tests should pass
* Add a failing test
* Make it pass
* Submit a pull request

== Copyright

Copyright (c) 2012 Attachments.me. See LICENSE.txt for
further details.

Add link to box api docs in readme

= ruby-box

Ruby SDK for Box API 2.0 (http://developers.box.com/docs/)

== Contributing to ruby-box

* Rename account.example to account.yml and fill in your Box credentials
* Type bundle install
* Type rake.. tests should pass
* Add a failing test
* Make it pass
* Submit a pull request

== Copyright

Copyright (c) 2012 Attachments.me. See LICENSE.txt for
further details.


= DESCRIPTION:

Applies base OS setup for Ubuntu, Windows, and CentOS systems

= REQUIREMENTS:

= ATTRIBUTES:

= USAGE:

The ondemand_server role should include each of the 3 recipes in its runlist.

Add change log to ondemand_base

= DESCRIPTION:

Applies base OS setup for Ubuntu, Windows, and CentOS systems

Changelog:

1.3:
* Installs vmware-tools
* Installs and configures NRPE including configuration of nrpe.cfg and installation of plugins
* Installs likewise the proper way avoiding some failure scenarios, which required systems be rebuilt
* Includes a new platform recipe case statement that allows for a simpler ondemand_server role configuration
* References ondemand_base for attributes and not ondemand_server, which was against best practices
* Properly sets file modes to match best practices
* Prevents the Windows recipe from running on non-Windows systems, which resulted in a chef-client crash
* Saves the node back to the Chef server to prevent run lists from being wiped if a run fails during provisioning
* Sets high performance Power configs on Windows systems
* Disables hibernation on Windows systems

= REQUIREMENTS:

= ATTRIBUTES:

= USAGE:

The ondemand_server role should include each of the 3 recipes in its runlist.


= Dot Files

These are config files to set up a system the way I like it.

Most of it is based on Ryan Bates dot files, who I'm really thankful.
You can see more information here: http://github.com/ryanb/dotfiles

== Installation

  git clone git://github.com/carlosantoniodasilva/dotfiles ~/.dotfiles
  cd ~/.dotfiles
  rake install

Update Readme with https link

= Dot Files

These are config files to set up a system the way I like it.

Most of it is based on Ryan Bates dot files, who I'm really thankful.
You can see more information here: http://github.com/ryanb/dotfiles

== Installation

  git clone https://github.com/carlosantoniodasilva/dotfiles.git ~/.dotfiles
  cd ~/.dotfiles
  rake install


== DiseasesMap

Application to build diseases on GoogleMaps

To use application need to execute

    rake db:migrate
    rails server -p"port"

On browser access

    localhost:"port"

Add more simple commands to use application

== DiseasesMap

Application to build diseases on GoogleMaps

To use application need to execute

    rake db:migrate
    bundle
    bundle exec rake assets:precompile
    rails server -p"port"

On browser access

    localhost:"port"


= LocalAssets

LocalAssets facilitates loading of assets normally served by various content delivery networks (CDNs) from local sources in development so your site loads faster, and works even when you don't have an Internet connection (eg, on an airplane).

To set up a local CDN mirror, see: http://github.com/alexreisner/cdn_mirror

== Rails

Add the gem to your +Gemfile+. Then add the following to your <tt>config/environments/development.rb</tt> file:

  config.middleware.use "Rack::LocalAssets", {
    "//ajax.googleapis.com/ajax/libs/" => "//localhost/cdn_mirror/google/"
  }

The configuration hash should contain any URL fragments that should be replaced with local alternatives in the development environment. The above example is for assets normally served by Google's CDN.

== Sinatra

require 'local_assets'

use Rack::LocalAssets, {
  "//ajax.googleapis.com/ajax/libs/" => "//localhost/cdn_mirror/google/"
}

== To-do List

* require replaced URLs to be in src or href attributes
* allow external config file which does not get committed to repo
  * allows different local URLs on different development machines
* implement as a railtie and load middleware automatically on app_middleware config hook

Copyright (c) 2009-10 Alex Reisner, released under the MIT license

Fix spacing (indent code for rdoc).


= CouchRestAdapter

This is a realy early version.

This project rocks and uses MIT-LICENSE.

== Requirements

* Rails > 4
* Couchrest
* Requires config/database.yml file

== Instalation

=== In Gemfile

    gem 'couch_rest_adapter'

=== Sample config/database.yml

    defaults: &defaults
      host: localhost
      port: 5984
      protocol: http

    development:
      <<: *defaults
      name: db

    test:
      <<: *defaults
      name: db_test

=== Model Declaration

  class User < CouchRestAdpater::Base
    use_default_database
  end

=== TODO

* Allow setting new attributes with ```model.attribute = value```
* More test coverage
* Add tasks for pushing design documents
* Add support for basic database http auth.

Add sample all couch view

= CouchRestAdapter

This is a realy early version.

This project rocks and uses MIT-LICENSE.

== Requirements

* Rails > 4
* Couchrest
* Requires config/database.yml file

== Instalation

=== In Gemfile

    gem 'couch_rest_adapter'

=== Sample config/database.yml

    defaults: &defaults
      host: localhost
      port: 5984
      protocol: http

    development:
      <<: *defaults
      name: db

    test:
      <<: *defaults
      name: db_test

=== CouchViews

In order for ```Model.all``` to workyou need to add a view like (code in cs):

    (d) ->
      split_id = d._id.split('/')
      t = split_id[0]
      emit t, d

We are planning to add a rake task that setup this view on install.

=== Model Declaration

  class User < CouchRestAdpater::Base
    use_default_database
  end

=== TODO

* Allow setting new attributes with ```model.attribute = value```
* More test coverage
* Add tasks for pushing design documents
* Add support for basic database http auth.


== README
In order to access the collegestar_org Rails app you must first do the following.
Install or mount Nfs via homebrew. http://www.cyberciti.biz/faq/apple-mac-osx-nfs-mount-command-tutorial/
Download and install vagrant to create vagrant files. https://www.vagrantup.com/downloads.html
Download and install virtual box. https://www.virtualbox.org/wiki/Downloads
Create a folder to house the development_box and collegestar_org app.
Create a rails virtual database in terminal using "$RAILS_ENV=test bin/rake db:create".
Navigate or cd to your collegestar_org directory and type the following commmands "$vagrant init", "$vagrant ssh", "$vagrant up", "$bin/rails server --binding 0.0.0.0" to launch the rails app.
Navigate to your preffered browser and input "http://localhost:3000/" as the url and the collegestar site should appear.
In order to exit enter the command "$exit" followed by either "$vagrant halt"(Recommended) or "$vagrant destroy"(Not Recommended).

<tt>rake doc:app</tt>.

Update Readme to correct spacing error

== README
1. In order to access the collegestar_org Rails app you must first do the following.

2. Install or mount Nfs via homebrew. http://www.cyberciti.biz/faq/apple-mac-osx-nfs-mount-command-tutorial/

3. Download and install vagrant to create vagrant files. https://www.vagrantup.com/downloads.html

4. Download and install virtual box. https://www.virtualbox.org/wiki/Downloads

5. Create a folder to house the development_box and collegestar_org app.

6. Create a rails virtual database in terminal using "$RAILS_ENV=test bin/rake db:create".

7. Navigate or cd to your collegestar_org directory and type the following commmands "$vagrant init", "$vagrant vb-guest", "$vagrant ssh", "$vagrant up", "$bin/rails server --binding 0.0.0.0" to launch the rails app.

8. Navigate to your preffered browser and input "http://localhost:3000/" as the url and the collegestar site should appear.

9. In order to exit enter the command "$exit" followed by either "$vagrant halt"(Recommended) or "$vagrant destroy"(Not Recommended).

<tt>rake doc:app</tt>.


= ColorboxRails

Make links open in lightbox (colorbox) a breeze

= Usage

in your application.css

<tt>//= require colorbox-rails</tt>

in your application.js

<tt>//= require colorbox-rails</tt>

Then enable link to be displayed in colorbox by simply adding :colorbox => true attribute. E.g.

<tt><%= link_to "My superb link", "#", :data => { :colorbox => true } %></tt>

My superb link

Add attributes inside the :data block

<tt><%= link_to "My superb link", "#", :data => { :colorbox => true, :colorbox_height => '300px', :colorbox_width => '300px', :colorbox_iframe => true } %></tt>

This project rocks and uses MIT-LICENSE.

Fix application.css syntax for require statement

= ColorboxRails

Make links open in lightbox (colorbox) a breeze

= Usage

in your application.css

<tt> *= require colorbox-rails</tt>

in your application.js

<tt>//= require colorbox-rails</tt>

Then enable link to be displayed in colorbox by simply adding :colorbox => true attribute. E.g.

<tt><%= link_to "My superb link", "#", :data => { :colorbox => true } %></tt>

My superb link

Add attributes inside the :data block

<tt><%= link_to "My superb link", "#", :data => { :colorbox => true, :colorbox_height => '300px', :colorbox_width => '300px', :colorbox_iframe => true } %></tt>

This project rocks and uses MIT-LICENSE.


== has_ratings

+has_ratings+ demonstrates a reference implementation for handling ratings.

== Resources

API

* http://api.pluginaweek.org/has_ratings

Bugs

* http://pluginaweek.lighthouseapp.com/projects/13276-has_ratings

Development

* http://github.com/pluginaweek/has_ratings

Source

* git://github.com/pluginaweek/has_ratings.git

== Description

Storing ratings is a pretty common task when building web applications with a
community-based focus.  Ratings can have names and values associated with them.
This plugin demonstrate a simple way to manage what ratings can be used and
how they are persisted.

== Usage

Note that this is a reference implementation and, most likely, should be
modified for your own usage.

=== Example

  user = User.find(1)
  video = Video.find(1)

  video.ratings.create(:rater => user, :value => :poor)

== Testing

Before you can run any tests, the following gem must be installed:
* plugin_test_helper[http://github.com/pluginaweek/plugin_test_helper]

To run against a specific version of Rails:

  rake test RAILS_FRAMEWORK_ROOT=/path/to/rails

== Dependencies

* Rails 2.1 or later
* plugins_plus[http://github.com/pluginaweek/plugins_plus]
* acts_as_enumeration[http://github.com/pluginaweek/acts_as_enumeration]

Use strings for reference rating values

== has_ratings

+has_ratings+ demonstrates a reference implementation for handling ratings.

== Resources

API

* http://api.pluginaweek.org/has_ratings

Bugs

* http://pluginaweek.lighthouseapp.com/projects/13276-has_ratings

Development

* http://github.com/pluginaweek/has_ratings

Source

* git://github.com/pluginaweek/has_ratings.git

== Description

Storing ratings is a pretty common task when building web applications with a
community-based focus.  Ratings can have names and values associated with them.
This plugin demonstrate a simple way to manage what ratings can be used and
how they are persisted.

== Usage

Note that this is a reference implementation and, most likely, should be
modified for your own usage.

=== Example

  user = User.find(1)
  video = Video.find(1)

  video.ratings.create(:rater => user, :value => 'poor')

== Testing

Before you can run any tests, the following gem must be installed:
* plugin_test_helper[http://github.com/pluginaweek/plugin_test_helper]

To run against a specific version of Rails:

  rake test RAILS_FRAMEWORK_ROOT=/path/to/rails

== Dependencies

* Rails 2.1 or later
* plugins_plus[http://github.com/pluginaweek/plugins_plus]
* acts_as_enumeration[http://github.com/pluginaweek/acts_as_enumeration]


= changelog_parser

A ruby gem for creating nice changelogs based on your git commits.

== Installation

`gem install changelog_parser`

== Usage

Just run `changelog` in your git directory to print out a changelog
for the last two versions in your gem.

== Contributing to changelog_parser

* 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.
* 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) 2014 David Elbe. See LICENSE.txt for
further details.

Add changelog notice about 'true' option.

= changelog_parser

A ruby gem for creating nice changelogs based on your git commits.

== Installation

`gem install changelog_parser`

== Usage

Just run `changelog` or `changelog true` in your git directory to print
out a changelog for the last two versions in your gem.

== Contributing to changelog_parser

* 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.
* 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) 2014 David Elbe. See LICENSE.txt for
further details.


= Ninoxe {<img src="https://codeclimate.com/badge.png" />}[https://codeclimate.com/github/dryade/ninoxe]

This project rocks and uses MIT-LICENSE.

Add build status with Travis

= Ninoxe {}[http://travis-ci.org/dryade/ninoxe]{}[https://codeclimate.com/github/dryade/ninoxe]

This project rocks and uses MIT-LICENSE.


= payone_connect

This is a super simple wrapper around the API for the payment service provider payone (http://www.payone.de)

== Installation

  gem install payone_connect

== Usage

  require 'payone_connect'

  payone = PayoneConnect.new(api_key,params_hash)
  puts payone.request[:status]

== 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.
* Send me a pull request. Bonus points for topic branches.

== Copyright

Copyright (c) 2009 Patrick Huesler. See LICENSE for details.

Fix invalid code example in readme

= payone_connect

This is a super simple wrapper around the API for the payment service provider payone (http://www.payone.de)

== Installation

  gem install payone_connect

== Usage

  require 'payone_connect'
  payone = PayoneConnect.new(payone_api_endpoint, params_hash)
  puts payone.request[:status]

== 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.
* Send me a pull request. Bonus points for topic branches.

== Copyright

Copyright (c) 2009 Patrick Huesler. See LICENSE for details.


= Qwerty

This project rocks and uses MIT-LICENSE.

gem 'qwerty'
rake qwerty_engine:install:migrations

todo:
rake qwerty_engine:install
  - create sample sitemp.rb
  - copy across views

Add note about running CKEditor rake task to generate javascript files (this does not use the assetpipe line)

= Qwerty

gem 'qwerty'
rake qwerty_engine:install:migrations
rails generate ckeditor:install

todo:
rake qwerty_engine:install
  - create sample sitemp.rb
  - copy across views

This project rocks and uses MIT-LICENSE.


* Bug fixes

  * Undefined words now show a cleaner error. This was apparently not fixed
    in the prior release

=== 1.0.0

* Major enhancements:

  * Change `list` flag to the `all` flag for more clarity.
  * Remove query from Urban::Web replace with random and search.
  * Add `url` flag to print the url of the definition.

* Minor enhancements:

  * Add this history file.
  * Add Urban::Web#fetch for fetching pages from urban dictionary.
  * Add examples to help.
  * Remove require 'rubygems' from program and lib.
  * Test now only stubs singleton instead of class.
  * Use ~> instead of >= on dependencies.
  * Replace OpenStruct in Urban::Dictionary with plain Struct.
  * Move Nokogiri call to Dictionary#process.

* Bug fixs:

  * Passing -v or --version no longer prints help.
  * Undefined words now show a clean error.
  * No internet connection now shows a clean error.
  * Invalid options now show a clean error.

Document lack of 1.8.6 support

* Major enhancements:

  * Remove official support for Ruby 1.8.6

* Bug fixes

  * Undefined words now show a cleaner error. This was apparently not fixed
    in the prior release

=== 1.0.0

* Major enhancements:

  * Change `list` flag to the `all` flag for more clarity.
  * Remove query from Urban::Web replace with random and search.
  * Add `url` flag to print the url of the definition.

* Minor enhancements:

  * Add this history file.
  * Add Urban::Web#fetch for fetching pages from urban dictionary.
  * Add examples to help.
  * Remove require 'rubygems' from program and lib.
  * Test now only stubs singleton instead of class.
  * Use ~> instead of >= on dependencies.
  * Replace OpenStruct in Urban::Dictionary with plain Struct.
  * Move Nokogiri call to Dictionary#process.

* Bug fixs:

  * Passing -v or --version no longer prints help.
  * Undefined words now show a clean error.
  * No internet connection now shows a clean error.
  * Invalid options now show a clean error.


= WebTailer

This project rocks and uses MIT-LICENSE.

Add how to install to readme

= WebTailer

This project rocks and uses MIT-LICENSE.

= Install

Add gem into Gemfile !

 gem 'web_tailer', :git => 'git://github.com/mewlist/web_tailer.git'

Add route to web_tailer into your config/routes.rb !

 mount WebTailer::Engine => '/web_tailer'

Add iframe into your view. and customize path param to what you want !

 <iframe src='web_tailer?path=/var/log/httpd/access.log'></iframe>

enjoy!


== Fair Use Tool

Fair Use Tool is an interactive online tool that will be accessible for middle-school students and their teachers. The main goal of the tool is designing and coding web application with Interactive and User-friendly Interface for teaching a playful way of how to use copyrighted content in accordance with fair use policy.

== License
Fair Use Tool project is licensed under The MIT License
Copyright (C) 2012 by Karim El Husseiny <kelhusseiny@cyber.law.harvard.ed>

Edit Lisence and Readme Description

== Fair Use Tool

Fair Use Tool is an interactive online tool that will be accessible for middle-school students and their teachers. The main goal of the tool is designing and coding web application with Interactive and User-friendly Interface for teaching a playful way of how to use copyrighted content in accordance with fair use policy.

== Requirements
= Main requirments
* ruby 1.9.3
* mysql 14.14
* rails 3.2.5
= Paperclip requirments
* ImageMagick 6.6.9
* Ghostscript 9.05

== License
*Fair Use Tool project is licensed under The MIT License.
*Copyright (C) 2012 by Karim El Husseiny <kelhusseiny@cyber.law.harvard.ed>


== README

This README would normally document whatever steps are necessary to get the
application up and running.

Things you may want to cover:

* Ruby version

* System dependencies

* Configuration

* Database creation

* Database initialization

* How to run the test suite

* Services (job queues, cache servers, search engines, etc.)

* Deployment instructions

* ...

Please feel free to use a different markup language if you do not plan to run
<tt>rake doc:app</tt>.

Update the readme to include some todos.

== Blinder

This is a work in progress! Of course, what isn't? Essentially, I wanna use this textbook Rails app
to handle RFP collections for SCRC. At some point, I'll have to write a _real_ README.

== TODO

Here's some todos I lifted from a recent commit:

* Add ordering for Blinds and Questions, then add those orders to the seed files.
* Add helpers to generate markup for each question kind.
* Add validation and persistence for Responses.
* Add editing ability via unique code generation after saving.


= Sinatra Application Template

Includes Bundler, RSpec, RCov, YARD, Haml and of course Sinatra

== Getting Started

Install Bundler (http://github.com/wycats/bundler)
  sudo gem install bundler

Runing Bundler
  gem bundle

== Run your application

  ./bin/rackup

== Compile stylesheets with LESS (http://lesscss.org/)

  ./bin/lessc styles/style.less public/css/style.css

== Run specs with RSpec (http://rspec.info/)

Run all specs
  ./bin/rake spec
Run all specs with coverage (http://eigenclass.org/hiki.rb?rcov)
  ./bin/rake rcov

== Generate documentation with YARD (http://yardoc.org/)

  ./bin/rake yarddoc

Make sure you are running the latest RubyGems >= 1.3.5

= Sinatra Application Template

Includes Bundler, RSpec, RCov, YARD, Haml and of course Sinatra

== Getting Started

Make sure you are running the latest RubyGems:
  sudo gem update --system

Install Bundler (http://github.com/wycats/bundler)
  sudo gem install bundler

Running Bundler
  gem bundle

== Run your application

  ./bin/rackup

== Compile stylesheets with LESS (http://lesscss.org/)

  ./bin/lessc styles/style.less public/css/style.css

== Run specs with RSpec (http://rspec.info/)

Run all specs
  ./bin/rake spec
Run all specs with coverage (http://eigenclass.org/hiki.rb?rcov)
  ./bin/rake rcov

== Generate documentation with YARD (http://yardoc.org/)

  ./bin/rake yard


= Respect plugin for Rails

Respect integration for Rails 3.x.

= Features

* Controllers' helpers to automatically validates and sanitize incoming parameters.
* A Rails engine to mount in your application to publish your public REST API documentation.
  * Read the full API documentation.
  * Query a particular route schema.
  * Query a particular controller's action schema.
  * A validator web service to test whether your clients request are valid.
* A DSL to group your requests and responses schema by controllers.

= License

This project rocks and uses MIT-LICENSE.

Improve a bit the features presentation.

= Respect plugin for Rails

Respect [FIXME:url] integration for Rails 3.x.

= Features

* Based on Respect [FIXME:url] to compactly specify your REST API.
* Controllers' helpers to automatically validates and sanitize incoming parameters.
* A Rails engine to mount in your application to publish your public REST API documentation.
  * Your documentation will always be up to date with your application.
  * Access the full API documentation.
  * Query a schema given a route or a controller's action.
  * A validator web service your clients can use to check their requests.
* A DSL to group your requests and responses schema by controllers.

= Getting started!

= License

This project rocks and uses MIT-LICENSE.


= define

define is a simple CLI to Google's define:word utility. Syntax is `define: word [or phrase]` to return Google's definitions.

== Copyright

Copyright (c) 2010 Trevor Hartman. See {LICENSE}[http://github.com/devth/define/blob/develop/LICENSE] for details.

Update docs with code formatting and more description.

= define

define is a simple CLI to Google's define:word utility. Syntax is [\+define: word [or phrase]+] to return Google's definitions. Quit wasting your time looking up definitions in a clunky old browser and let command line define build your vocabulary minimalistically!

== Copyright

Copyright (c) 2010 Trevor Hartman. See {LICENSE}[http://github.com/devth/define/blob/develop/LICENSE] for details.


= RailsCommon

This project rocks and uses MIT-LICENSE.

Add the code climate badge, and the gemnasium.


= rat

Ruby interface to Unix "at" command.

== Installation

  $ gem sources -a http://gems.github.com  # you only need to run this once
  $ sudo gem install koops-rat

== Usage

  $ require 'rat'
  $ job = Rat.add('touch at-at', Time.now + 30)
  $ # => <integer id>
  $ # Thirty seconds later, the touch command runs.
  $ Rat.list
  $ # => [{:job => <integer id>, :time => Thu Oct 08 09:08:51 -0700 2009}, ...]
  $ Rat.delete(job) # if you change your mind about running the command.

== Notes
"At" stores your environment, including your working directory, so you don't need full pathnames to executables, etc. like you do in cron (though it doesn't hurt).

== MacOS X

Note that, by default, "at" is disabled on MacOS X.  See "man atrun" for the command to enable it.

== Copyright

Copyright (c) 2009 Ryan Koopmans. See LICENSE for details.

Change install location to gemcutter.

= rat

Ruby interface to Unix "at" command.

== Installation

  $ gem sources -a http://gemcutter.org
  $ sudo gem install rat

== Usage

  $ require 'rat'
  $ job = Rat.add('touch at-at', Time.now + 30)
  $ # => <integer id>
  $ # Thirty seconds later, the touch command runs.
  $ Rat.list
  $ # => [{:job => <integer id>, :time => Thu Oct 08 09:08:51 -0700 2009}, ...]
  $ Rat.delete(job) # if you change your mind about running the command.

== Notes
"At" stores your environment, including your working directory, so you don't need full pathnames to executables, etc. like you do in cron (though it doesn't hurt).

== MacOS X

Note that, by default, "at" is disabled on MacOS X.  See "man atrun" for the command to enable it.

== Copyright

Copyright (c) 2009 Ryan Koopmans. See LICENSE for details.


= versatile_rjs

Writing dynamic HTML apps in only Ruby, without JavaScript.

== How to use

If the JavaScript framework your Rails app depends on is jQuery, the only thing you must do is to write the statements below in your Gemfile:

 gem 'versatile_rjs'

== Contributing to versatile_rjs

* 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.
* 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) 2011 Kevin IMAI TOYODA See LICENSE.txt for
further details.

Add term till 2012 at the Copyright section.

= versatile_rjs

Writing dynamic HTML apps in only Ruby, without JavaScript.

== How to use

If the JavaScript framework your Rails app depends on is jQuery, the only thing you must do is to write the statements below in your Gemfile:

 gem 'versatile_rjs'

== Contributing to versatile_rjs

* 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.
* 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) 2011-2012 Kevin IMAI TOYODA See LICENSE.txt for
further details.


= CSS3 Buttons

This is a collection of buttons that show what is possible using CSS3. Almost all of these buttons look best in Chrome (followed by Safari, then Firefox, with all other browsers being irrelevant for the purposes of this exercise).

Currently the buttons look like this:

http://dl.dropbox.com/u/2483533/buttons/buttons.png

Update readme to link to preview

= CSS3 Buttons

This is a collection of buttons that show what is possible using CSS3. Almost all of these buttons look best in Chrome (followed by Safari, then Firefox, with all other browsers being irrelevant for the purposes of this exercise).

View the buttons here: <a href="http://ubuwaits.github.com/css3-buttons/">http://ubuwaits.github.com/css3-buttons/<a>


=== Ben Orenstein's dot files

These are config files to set up a system the way I like it.

Vim-users will likely find useful stuff in .vimrc, and also vim/snippets.

I'm also a pretty aggressive aliaser. You might find a few you like in bash/aliases.

== Installation

  git clone git://github.com/r00k/dotfiles ~/.dotfiles
  cd ~/.dotfiles
  rake install

  Vim plugins are managed through vundle. You'll need to install vundle to get them.

  git clone https://github.com/gmarik/vundle.git ~/.vim/bundle/vundle
  Run :BundleInstall in vim.

Adjust the readme for the fork

=== Einar Jonsson's dot files
This is more or less a rip-off from Ben Orenstein's dot files

== Installation

  git clone git://github.com/einarj/dotfiles ~/.dotfiles
  cd ~/.dotfiles
  rake install

  Vim plugins are managed through vundle. You'll need to install vundle to get them.

  git clone https://github.com/gmarik/vundle.git ~/.vim/bundle/vundle
  Run :BundleInstall in vim.


= MaskableAttribute

This project rocks and uses MIT-LICENSE.

Add Setup Instructions for Testing

= MaskableAttribute

This project rocks^H^H^H^H sucks and uses MIT-LICENSE.

Steps to test:
1. <tt>cd test/dummy</tt>
2. <tt>rake db:migrate</tt>
3. <tt>rake db:test:clone</tt>
4. <tt>cd -</tt>
5. <tt>rake test</tt>


= Ninoxe {}[http://travis-ci.org/dryade/ninoxe]{}[https://codeclimate.com/github/dryade/ninoxe]

This project rocks and uses MIT-LICENSE.

Add space for build status and code climate

= Ninoxe {}[http://travis-ci.org/dryade/ninoxe] {}[https://codeclimate.com/github/dryade/ninoxe]

This project rocks and uses MIT-LICENSE.


= paypal-express

Handle PayPal Express Checkout.
Both Instance Payment and Recurring Payment are supported.
Express Checkout for Digital Goods is also supported.

{<img src="https://travis-ci.org/ianfleeton/paypal-express.svg" />}[https://travis-ci.org/ianfleeton/paypal-express]

== Why this fork?

The original gem is not maintained and has broken compatibility with current PayPal APIs.
You can use this fork which is actively maintained to ensure it is working properly.

== Installation

Add to your Gemfile
  gem 'ianfleeton-paypal-express', github: 'ianfleeton/paypal-express', require: 'paypal/express'
Or
  gem 'ianfleeton-paypal-express', require: 'paypal/express'

== Usage

See Wiki on Github
https://github.com/nov/paypal-express/wiki

Play with Sample Rails App
https://github.com/nov/paypal-express-sample
https://paypal-express-sample.heroku.com

== 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 © 2011 Ian Fleeton, nov matake. See LICENSE for details.

Update link to newly cloned wiki

= paypal-express

Handle PayPal Express Checkout.
Both Instance Payment and Recurring Payment are supported.
Express Checkout for Digital Goods is also supported.

{<img src="https://travis-ci.org/ianfleeton/paypal-express.svg" />}[https://travis-ci.org/ianfleeton/paypal-express]

== Why this fork?

The original gem is not maintained and has broken compatibility with current PayPal APIs.
You can use this fork which is actively maintained to ensure it is working properly.

== Installation

Add to your Gemfile
  gem 'ianfleeton-paypal-express', github: 'ianfleeton/paypal-express', require: 'paypal/express'
Or
  gem 'ianfleeton-paypal-express', require: 'paypal/express'

== Usage

See Wiki on Github
https://github.com/ianfleeton/paypal-express/wiki

Play with Sample Rails App
https://github.com/nov/paypal-express-sample
https://paypal-express-sample.heroku.com

== 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 © 2011 Ian Fleeton, nov matake. See LICENSE for details.


= gettext_column_mapping

If you use mutoh/gettext or grosser/fast_gettext to localize your active_record models, this library is for you.

== 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.

== Requirements
* mutoh/gettext_activerecord >= 2.1.0 or grosser/fast_gettext
* rails >= 2.2

== Features/Problems
This library is extracted from another application with its requirements.  So it may not fit your project
It must be refactored and improved.

* Must be Rails independent
* Must have a better API methods naming
* Must write a documentation.
* Must write tests.

Example
=======

Example goes here.

== Maintainer
Ramihajamalala Hery <hery at rails-royce.org>

== Copyright

Copyright (c) 2010 [Ramihajamalala Hery <hery at rails-royce.org], released under the MIT license

Update TODO list + fix presentation

= gettext_column_mapping

If you use mutoh/gettext or grosser/fast_gettext to localize your active_record models, this library is for you.

== 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.

== Requirements
* mutoh/gettext_activerecord >= 2.1.0 or grosser/fast_gettext
* rails >= 2.2

== Features/Problems
This library is extracted from another application with its requirements.  So it may not fit your project
It must be refactored and improved.

* Must have a better API methods naming
* Must write a documentation.
* Improve tests
* Must accept different output than UTF-8

== Example

Example goes here.

== Maintainer
Ramihajamalala Hery <hery at rails-royce.org>

== Copyright

Copyright (c) 2010 [Ramihajamalala Hery <hery at rails-royce.org], released under the MIT license


= inline_forms

Ever tired of setting up forms to manage your data? Inline Forms aims at quick and easy setup of models, migrations and controllers and providing a user-friendly interface.

= Usage

Look in the generator files for a hint about usage. In short:
 rails g inline_forms Person first_name:string last_name:string age:dropdown_with_integers
will create a model, a migration an a controller. In the model you would only have to add
values for the dropdown, or instance 12..45.
In going to /persons you would see a nice form to add and edit persons.

It's work in progress.

== Contributing to inline_forms

* 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.
* 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) 2011 Ace Suares. See LICENSE.txt for
further details.

Fix typo: ...for instance... rather than ...or instance...

= inline_forms

Ever tired of setting up forms to manage your data? Inline Forms aims at quick and easy setup of models, migrations and controllers and providing a user-friendly interface.

= Usage

Look in the generator files for a hint about usage. In short:
 rails g inline_forms Person first_name:string last_name:string age:dropdown_with_integers
will create a model, a migration an a controller. In the model you would only have to add
values for the dropdown, for instance 12..45.
In going to /persons you would see a nice form to add and edit persons.

It's work in progress.

== Contributing to inline_forms

* 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.
* 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) 2011 Ace Suares. See LICENSE.txt for
further details.


= CanCan Specs

== Running the specs

To run the specs first run the +bundle+ command to install the necessary gems and the +rake+ command to run the specs.

  bundle

Then run the appraisal command to install all the necessary test sets:

  appraisal install

You can then run all test sets:

  appraisal rake

Or individual ones:

  appraisal rails_3.0 rake

A list of the tests is in the +Appraisal+ file.

The specs support Ruby 1.8.7+

== Model Adapters

The model adapter ENV setting has been removed and replaced with the +Appraisal+ file.

Change spec readme for running individual specs

= CanCan Specs

== Running the specs

To run the specs first run the +bundle+ command to install the necessary gems and the +rake+ command to run the specs.

  bundle

Then run the appraisal command to install all the necessary test sets:

  appraisal install

You can then run all test sets:

  appraisal rake

Or individual ones:

  appraisal activerecord_3.2 rake

A list of the tests is in the +Appraisal+ file.

The specs support Ruby 1.8.7+

== Model Adapters

The model adapter ENV setting has been removed and replaced with the +Appraisal+ file.


= kit_kat_finger

A little game with a brand new name that probably violates a trademark

== How to play!

1. Download source
2. Run `bundle install`
3. Run `ruby -Ilib ./bin/kkf`
4. Follow instructions!

== To-do

* Game tests
* Better board tests
* Smarter computer play/strategy
* Variable randomness for difficulty settings

== Contributing to kit_kat_finger

* Not accepting contributions. I did this for me.

== Copyright

Copyright (c) 2017 Floyd Wright. See LICENSE.txt for
further details.

Add gem package to to-do

= kit_kat_finger

A little game with a brand new name that probably violates a trademark

== How to play!

1. Download source
2. Run `bundle install`
3. Run `ruby -Ilib ./bin/kkf`
4. Follow instructions!

== To-do

* Game tests
* Better board tests
* Package gem into CL tool
* Smarter computer play/strategy
* Variable randomness for difficulty settings

== Contributing to kit_kat_finger

* Not accepting contributions. I did this for me.

== Copyright

Copyright (c) 2017 Floyd Wright. See LICENSE.txt for
further details.


= Redmine pwauth plugin

Adds the +pwauth+ authentication to {Redmine}[https://www.redmine.org/].

== Requirements

The plugin requires {pwauth}[https://code.google.com/p/pwauth/] to be installed,
configured, and available in +PATH+, i.e. the user under which Redmine is run
can execute +pwauth+ without specifying a full path to this program.

The plugin was tested under Redmine versions 2.3 through 2.6.

== Installation

Before installing, make sure to stop Redmine. Then, perform the following
steps:

1. <tt>cd [redmine-install-dir]</tt>
2. <tt>git clone git://github.com/s3rvac/redmine_pwauth.git plugins/redmine_pwauth</tt>
3. <tt>RAILS_ENV=production rake redmine:plugins:migrate</tt>

After that, you can start Redmine and set the +pwauth+ authentication method
for the users of your choice (visit <tt>Administration > Users</tt>).

== Uninstallation

First, disable the +pwauth+ method for all users (visit <tt>Administration >
Users</tt>), and stop Redmine. Then, perform the following steps:

1. <tt>cd [redmine-install-dir]</tt>
2. <tt>RAILS_ENV=production rake redmine:plugins:migrate NAME=redmine_pwauth VERSION=0</tt>
3. <tt>rm -rf plugins/redmine_pwauth</tt>

After that, you can start Redmine.

Update the link to pwauth.

= Redmine pwauth plugin

Adds the +pwauth+ authentication to {Redmine}[https://www.redmine.org/].

== Requirements

The plugin requires {pwauth}[https://github.com/phokz/pwauth] to be installed,
configured, and available in +PATH+, i.e. the user under which Redmine is run
can execute +pwauth+ without specifying a full path to this program.

The plugin was tested under Redmine versions 2.3 through 2.6.

== Installation

Before installing, make sure to stop Redmine. Then, perform the following
steps:

1. <tt>cd [redmine-install-dir]</tt>
2. <tt>git clone git://github.com/s3rvac/redmine_pwauth.git plugins/redmine_pwauth</tt>
3. <tt>RAILS_ENV=production rake redmine:plugins:migrate</tt>

After that, you can start Redmine and set the +pwauth+ authentication method
for the users of your choice (visit <tt>Administration > Users</tt>).

== Uninstallation

First, disable the +pwauth+ method for all users (visit <tt>Administration >
Users</tt>), and stop Redmine. Then, perform the following steps:

1. <tt>cd [redmine-install-dir]</tt>
2. <tt>RAILS_ENV=production rake redmine:plugins:migrate NAME=redmine_pwauth VERSION=0</tt>
3. <tt>rm -rf plugins/redmine_pwauth</tt>

After that, you can start Redmine.


= changelogparser

Description goes here.

== Contributing to changelogparser

* 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.
* 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) 2014 David Elbe. See LICENSE.txt for
further details.

Update readme with installation instructions

= changelog_parser

A ruby gem for creating nice changelogs based on your git commits.

== Installation

`gem install changelog_parser`

== Usage

Just run `changelog` in your git directory to print out a changelog
for the last two versions in your gem.

== Contributing to changelog_parser

* 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.
* 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) 2014 David Elbe. See LICENSE.txt for
further details.


== Pull Request 20015-08-06

Changes implemented per vimeo's updated api:

* [Endpoint](https://developer.vimeo.com/apis/oembed#endpoint)
* [base_uri](https://developer.vimeo.com/apis/oembed#json-example)
* [info parameters](https://developer.vimeo.com/apis/oembed#json-example)

== 1.0.0, released 2009-09-28

* Upgraded to v2 of the API.
* Added some upload helpers.
* Huge refactor for the Advanced API making it easier to add/modify method calls.

== 0.2.2, released 2009-04-21

* Removed CGI escapes. Vimeo should be handling them on their end.

== 0.2.1, released 2009-01-06

* Last version was missing files.

== 0.2.0, released 2009-01-06

* Major re-factor of each request method.
* Separated the simple and advanced APIs into their own modules.
* Added some documentation.
* Updated the README.

== 0.1.2, released 2008-10-26

* Initial release

Format embedded links per rdoc

== Pull Request 20015-08-06

Changes implemented per vimeo's updated api:

* Endpoint [https://developer.vimeo.com/apis/oembed#endpoint]
* base_uri [https://developer.vimeo.com/apis/oembed#json-example]
* {info parameters}(https://developer.vimeo.com/apis/oembed#json-example)

== 1.0.0, released 2009-09-28

* Upgraded to v2 of the API.
* Added some upload helpers.
* Huge refactor for the Advanced API making it easier to add/modify method calls.

== 0.2.2, released 2009-04-21

* Removed CGI escapes. Vimeo should be handling them on their end.

== 0.2.1, released 2009-01-06

* Last version was missing files.

== 0.2.0, released 2009-01-06

* Major re-factor of each request method.
* Separated the simple and advanced APIs into their own modules.
* Added some documentation.
* Updated the README.

== 0.1.2, released 2008-10-26

* Initial release


= Appsterdam Members Listing

We're in full development mode. For background chatter about the development process, check: @appsterdamrs, @fngtps, @alloy, @thijs.

If you want to know what we're building, you can read the {requirements}[https://raw.github.com/Fingertips/appsterdam/master/design/requirements.html].

== Development

First do the regular Rails 3 dance.

    $ bundle install
    $ rake db:setup
    $ cp config/initializers/twitter.example.rb config/initializers/twitter.rb
    $ open config/initializers/twitter.rb

Fix the consumer credentials.

After that install Sphinx

    $ brew instal sphinx
    $ rake ts:index
    $ rake ts:start

Add note about purge_outdated_classifieds cron job.

= Appsterdam Members Listing

We're in full development mode. For background chatter about the development process, check: @appsterdamrs, @fngtps, @alloy, @thijs.

If you want to know what we're building, you can read the {requirements}[https://raw.github.com/Fingertips/appsterdam/master/design/requirements.html].

== Development

First do the regular Rails 3 dance.

    $ bundle install
    $ rake db:setup
    $ cp config/initializers/twitter.example.rb config/initializers/twitter.rb
    $ open config/initializers/twitter.rb

Fix the consumer credentials.

After that install Sphinx

    $ brew instal sphinx
    $ rake ts:index
    $ rake ts:start

== Production

Add a cron job which runs once every day that purges outdated classifieds:

    0 0 * * * cd /path/to/app && /usr/local/bin/bundle exec /usr/local/rake purge_outdated_classifieds


= iPojo support for buildr

iPojo is an OSGi component model (http://felix.apache.org/site/apache-felix-ipojo.html).
This extension processes OSGi bundles using iPojo's pojoizer to generate the required
metadata for the iPojo component model.

The extension will process all packages of type :jar and generate the required metadata
from annotations and an ipojo metadata file if present. The default location of the
metadata file is "src/main/config/ipojo.xml" but this can be changed by assigning the
"ipojo.metadata_filename" setting.

A typical project that uses the extension with the default metadata file location.

  define 'myProject' do
    ...
    project.ipojoize!
    package :jar
    ...
  end

An example of a project that specifies the metadata file location.

  define 'myProject' do
    ...
    # Note: no longer require project.pojoize!
    project.ipojo.metadata_filename = _("src/ipojo.xml")
    package :jar
    ...
  end

== Installation

The extension is packaged as a gem named "buildr-ipojo", consult the ruby gems installation
steps but typically it is either

  sudo gem install buildr-ipojo

for MRI ruby or

  jgem install buildr-ipojo

for jruby.

The user then needs to add the following require into the build file:

  require 'buildr_ipojo'

If the local maven repository does not contain the required ipojo jars they can be downloaded
but you will need to register the remote repository by adding the following to the build file:

repositories.remote << Buildr::Ipojo.remote_repository

Indent the section regarding adding repositories


= IronRubyInline

Allows C#, F#, and Visual Basic code to be compiled inline with IronRuby code.

== usage

  gem 'iron_ruby_inline'
  require 'iron_ruby_inline'

== examples

%Q{
public class CsCat
{
    public void Greet()
    {
        System.Console.WriteLine("Hai  u!");
    }
}
}.compile

cscat = CsCat.new
cscat.greet # Hai u!

%Q{
namespace Lolz
type Cat() =
    member this.Greet() =
        printfn "Hai u!"
}.compile(:language => :fs)

fscat = Lolz::Cat.new
fscat.greet # Hai u!

== Copyright

Copyright (c) 2009 Ray Vernagus. See LICENSE for details.

Add pre tags to code examples.


= capistrano-notification

Description goes here.

== 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) 2010 Keita Urashima. See LICENSE for details.

Add a description and usage.

= capistrano-notification

This allow to notify the end of the deployment on IRC.

== Usage

  require 'capistrano-notification'

  notification.irc do |irc|
    irc.host    'chat.freenode.net'
    irc.channel '#rubykaigi.org'
    irc.message { "#{local_user} deployed #{application} to #{deploy_target}" }
  end

== 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) 2010 Keita Urashima. See LICENSE for details.


= naglfar

This gem does nothing but declare the Naglfar class. But you do want a Naglfar in case of the Ragnarök, don't you?

== 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) 2010 Dimitri Krassovski. See LICENSE for details.

Add badges to the readme

{}[https://travis-ci.org/labria/naglfar]
{}[https://codeclimate.com/github/labria/naglfar]

= naglfar

This gem does nothing but declare the Naglfar class. But you do want a Naglfar in case of the Ragnarök, don't you?

== 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) 2010 Dimitri Krassovski. See LICENSE for details.


Update ReadMe with application instructions

== README

Hello!

This here is a Reddit clone I made with Rails.

How to run this app

* git clone into a local directory

* cd into repository

* Run <tt>bundle install</tt>

* Run <tt>bundle exec rake db:create</tt>

* Run <tt>bundle exec rake db:migrate</tt>

* Run <tt>rails server</tt>

* Go to <tt>http://localhost:3000/</tt> via your browser.

Please email me with any questions at christophermamian@gmail.com


= BitField

 This C extension wraps boost::dynamic_bitset and makes it available
as a native Ruby class. The bitset behaves like an an array allowing
only values of 0 and 1. Using this extension is easy:

    b = BitField.new 10 # Initializes BitField with size 10
    puts b              # Prints '0000000000' where the last bit is b[0]
    b[0..3] = Array.new(4) {1}  # Sets bits 0 to 3 to 1

Note that in contrast to the Ruby Array behaviour the BitField does not
automatically grow in size.

= Licence
Copyright(c) 2011 Fabian Becker, released under 2-clause BSD licence.

Fix indent for first text-line


== twitter-text-objc

Objective-C port of the twitter-text handling libraries.

This library supports OS X 10.7+ and iOS 4+, both ARC and non-ARC environments.

== Set up Xcode

Make sure Xcode 4.3+ is already installed. Install the Command Line Tools in Xcode.

  Preferences -> Downloads -> Command Line Tools

Run the following command, so that we can use xcodebuild:

  sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer

== Tests

To run the Conformance test suite, simply run rake:

  rake

Once you ran rake, you can run the tests in Xcode. Open testproject/TwitterText.xcodeproj with Xcode and hit Cmd+U.

== Issues

Have a bug? Please create an issue here on GitHub!

https://github.com/twitter/twitter-text-objc/issues

== To Do

* None

== Authors

* Satoshi Nakagawa

== License

Copyright 2012 Twitter, Inc.

Licensed under the Apache License, Version 2.0: http://www.apache.org/licenses/LICENSE-2.0

Add link to author's github account.

== twitter-text-objc

Objective-C port of the twitter-text handling libraries.

This library supports OS X 10.7+ and iOS 4+, both ARC and non-ARC environments.

== Set up Xcode

Make sure Xcode 4.3+ is already installed. Install the Command Line Tools in Xcode.

  Preferences -> Downloads -> Command Line Tools

Run the following command, so that we can use xcodebuild:

  sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer

== Tests

To run the Conformance test suite, simply run rake:

  rake

Once you ran rake, you can run the tests in Xcode. Open testproject/TwitterText.xcodeproj with Xcode and hit Cmd+U.

== Issues

Have a bug? Please create an issue here on GitHub!

https://github.com/twitter/twitter-text-objc/issues

== To Do

* None

== Authors

* Satoshi Nakagawa https://github.com/psychs

== License

Copyright 2012 Twitter, Inc.

Licensed under the Apache License, Version 2.0: http://www.apache.org/licenses/LICENSE-2.0


= My dot files

== Prerequisites

* A working RVM installation
* A terminal with support for 256 colors (<tt>TERM=xterm-256color</tt>)

== Installation

  brew install fish
  chsh -s /usr/local/bin/fish
  git clone git://github.com/der-flo/dotfiles ~/dotfiles
  cd ~/dotfiles
  rake install

== More

Configured font in terminal:
[Bitsteam Vera Sans Mono Nerd Font Complete Mono](https://github.com/ryanoasis/nerd-fonts#patched-fonts)
in size 13pt.

== Inspirations

Inspired by or shamelessly copied from

* https://github.com/ryanb/dotfiles
* https://github.com/thoughtbot/dotfiles
* https://github.com/skwp/dotfiles

Add ripgrep to install docs

= My dot files

== Prerequisites

* A working RVM installation
* A terminal with support for 256 colors (<tt>TERM=xterm-256color</tt>)

== Installation

  brew install fish ripgrep
  chsh -s /usr/local/bin/fish
  git clone git://github.com/der-flo/dotfiles ~/dotfiles
  cd ~/dotfiles
  rake install

== More

Configured font in terminal:
[Bitsteam Vera Sans Mono Nerd Font Complete Mono](https://github.com/ryanoasis/nerd-fonts#patched-fonts)
in size 13pt.

== Inspirations

Inspired by or shamelessly copied from

* https://github.com/ryanb/dotfiles
* https://github.com/thoughtbot/dotfiles
* https://github.com/skwp/dotfiles


= Stripe Python bindings

== Installation

You don't need this source code unless you want to modify the
package. If you just want to use the Stripe Python bindings, you
should run [1]:

  sudo pip --index-url https://code.stripe.com --upgrade stripe

To install from source, run:

  python setup.py install

== Documentation

Please see https://stripe.com/api for the most up-to-date
documentation.

[1] See http://www.pip-installer.org/en/latest/index.html for
instructions on installing pip. If you are on a system with
easy_install but not pip, you can use easy_install instead.

Reformat instructions for installing pip

= Stripe Python bindings

== Installation

You don't need this source code unless you want to modify the
package. If you just want to use the Stripe Python bindings, you
should run:

  sudo pip --index-url https://code.stripe.com --upgrade stripe

To install from source, run:

  python setup.py install

(See http://www.pip-installer.org/en/latest/index.html for
instructions on installing pip. If you are on a system with
easy_install but not pip, you can use easy_install instead.)

== Documentation

Please see https://stripe.com/api for the most up-to-date
documentation.


= versioneye-core

<img src="https://www.codeship.io/projects/89b50ff0-9c04-0131-2ec8-3af16e33d613/status" />

This project contains the core elements of VersionEye. This project is used by the WWW server and the API.

Remove broken link from readme

= versioneye-core

This project contains the core elements of VersionEye. This project is used by the WWW server and the API.


== README

[![Build Status](https://travis-ci.org/Coolnesss/BestRecipe.svg?branch=master)](https://travis-ci.org/Coolnesss/BestRecipe)
[![Code Climate](https://codeclimate.com/github/Coolnesss/BestRecipe/badges/gpa.svg)](https://codeclimate.com/github/Coolnesss/BestRecipe)

This will be the best recipe thing by Chang and Juho!

This README would normally document whatever steps are necessary to get the
application up and running.

Things you may want to cover:

* Ruby version

* System dependencies

* Configuration

* Database creation

* Database initialization

* How to run the test suite

* Services (job queues, cache servers, search engines, etc.)

* Deployment instructions

* ...

Please feel free to use a different markup language if you do not plan to run
<tt>rake doc:app</tt>.

Fix travis and code climate badges

== README

{}[https://travis-ci.org/Coolnesss/BestRecipe]
{}[https://codeclimate.com/github/Coolnesss/BestRecipe]
{}[https://codeclimate.com/github/Coolnesss/BestRecipe]

This will be the best recipe thing by Chang and Juho!

This README would normally document whatever steps are necessary to get the
application up and running.

Things you may want to cover:

* Ruby version

* System dependencies

* Configuration

* Database creation

* Database initialization

* How to run the test suite

* Services (job queues, cache servers, search engines, etc.)

* Deployment instructions

* ...

Please feel free to use a different markup language if you do not plan to run
<tt>rake doc:app</tt>.


== Big Gollum

{<img src="https://badges.gitter.im/Join%20Chat.svg" alt="Join the chat at https://gitter.im/oponder/big-gollum">}[https://gitter.im/oponder/big-gollum?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge]

Create, destroy, and manage permissions to multiple gollum wiki's

Right now all the app does is let you create a gollum wiki and then browse and edit it.

== Intended Use Case

I want to be able to quickly create a wiki and invite others people to manage/view it.

== How does it work?

There is a route that mounts a small rack app I made called WikiMounter.

WikiMounter delegates its call to Precious (The gollum front end) but configures it so the links still work.

== How to start it?

    bundle install
    rake db:migrate
    rails s

You can then follow the start up process. When there are no user
accounts in the database the app will ask you to create the first admin account.

Once you are logged in you can click on add wiki, give it a name (No spaces or
weird characters) and then you will be able to click on your wiki and browse/edit it.

You can then click on add wiki, give it a name (No spaces or weird characters) and then you will be able to click on your wiki and browse/edit it.

== License

MIT License.

Add contributers / thanks to readme

== Big Gollum

{<img src="https://badges.gitter.im/Join%20Chat.svg" alt="Join the chat at https://gitter.im/oponder/big-gollum">}[https://gitter.im/oponder/big-gollum?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge]

Create, destroy, and manage permissions to multiple gollum wiki's

Right now all the app does is let you create a gollum wiki and then browse and edit it.

== Intended Use Case

I want to be able to quickly create a wiki and invite others people to manage/view it.

== How does it work?

There is a route that mounts a small rack app I made called WikiMounter.

WikiMounter delegates its call to Precious (The gollum front end) but configures it so the links still work.

== How to start it?

    bundle install
    rake db:migrate
    rails s

You can then follow the start up process. When there are no user
accounts in the database the app will ask you to create the first admin account.

Once you are logged in you can click on add wiki, give it a name (No spaces or
weird characters) and then you will be able to click on your wiki and browse/edit it.

You can then click on add wiki, give it a name (No spaces or weird characters) and then you will be able to click on your wiki and browse/edit it.

== Contributors / Thanks

Scott Weldon (501st-alpha1)
Bob Forma

== License

MIT License.


= amee-abstraction-layer-gem

Description goes here.

== 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) 2010 George Palmer. See LICENSE for details.

Update readme with warning not safe for production

= Rails Abstraction Layer for AMEE

This is an rails abstraction layer for projects using the AMEE gem.  It is currently work in progress and not suitable for production use

== 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) 2010 George Palmer. See LICENSE for details.


== README

{}[https://travis-ci.org/Coolnesss/BestRecipe]
{}[https://codeclimate.com/github/Coolnesss/BestRecipe]
{}[https://codeclimate.com/github/Coolnesss/BestRecipe]

This will be the best recipe thing by Chang and Juho!

https://bestrecipe.herokuapp.com/

Add link to Trello board

== README

{}[https://travis-ci.org/Coolnesss/BestRecipe]
{}[https://codeclimate.com/github/Coolnesss/BestRecipe]
{}[https://codeclimate.com/github/Coolnesss/BestRecipe]

This will be the best recipe thing by Chang and Juho!

https://bestrecipe.herokuapp.com/

{Trello board}[https://trello.com/b/BwtZyRGY/bestrecipe]


= quick_config

Configure your web service dependencies with environment variables or local dotfiles and keep your credentials out of
your repository.

== Contributing to quick_config

* 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.
* 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) 2011 Jimmy Thrasher. See LICENSE.txt for
further details.

Add a bit to the readme

= quick_config

Configure your web service dependencies with environment variables or local dotfiles and keep your credentials out of
your repository.

Inspired by aspects of http://12factor.net

== Contributing to quick_config

* 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.
* 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) 2011 Jimmy Thrasher. See LICENSE.txt for
further details.


= HTML5 Support

The aim of HTML5 is to seamlessly provide support an extremely lightweight plugin for a few commonly used html5 attributes for browsers that don't already support them.

HTML5 Support currently supports the placeholder attribute and the autofocus attribute.
HTML5 Also supports type="password" fields, by special casing them, and swapping elements.

== Example

=== HTML

	<input type="text" autofocus />
	<input type="text" placeholder="Search Here" name="q" />
	<input type="password" placeholder="Password" name="pass" />

=== jQuery

  $(document).ready(function() {
	  $.html5support();

	  // or you can also run only support for what you want
	  $.placeholder();
	  // - or -
	  $.autofocus();
	});

=== CSS

Use this CSS if you would like your placeholder text to show up grey in browsers that do not natively support placeholder.

  .placeholder{ color: #888; }

== TODO

Support could be added for more HTML5 features. Ideas:

* <input pattern="/regex/" />

== License

HTML5 Support is licensed under the MIT License. See the MIT-License.txt file for full details.

Fix readme formatting on github

= HTML5 Support

The aim of HTML5 is to seamlessly provide support an extremely lightweight plugin for a few commonly used html5 attributes for browsers that don't already support them.

HTML5 Support currently supports the placeholder attribute and the autofocus attribute.
HTML5 Also supports type="password" fields, by special casing them, and swapping elements.

== Example

=== HTML

    <input type="text" autofocus />
    <input type="text" placeholder="Search Here" name="q" />
    <input type="password" placeholder="Password" name="pass" />

=== jQuery

    $(document).ready(function() {
      $.html5support();

      // or you can also run only support for what you want
      $.placeholder();
      // - or -
      $.autofocus();
    });

=== CSS

Use this CSS if you would like your placeholder text to show up grey in browsers that do not natively support placeholder.

    .placeholder{ color: #888; }

== TODO

Support could be added for more HTML5 features. Ideas:

* `<input pattern="/regex/" />`

== License

HTML5 Support is licensed under the MIT License. See the MIT-License.txt file for full details.


= groupr

Description goes here.

== Contributing to groupr

* 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.
* 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) 2012 Nikky Southerland. See LICENSE.txt for
further details.

Add travis-ci image to readme

{<img src="https://travis-ci.org/allynfolksjr/groupr.png" />}[https://travis-ci.org/allynfolksjr/groupr]]

= groupr

Description goes here.

== Contributing to groupr

* 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.
* 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) 2012 Nikky Southerland. See LICENSE.txt for
further details.


= Local CDN

Local CDN simplifies the inclusion of external stylesheets and JavaScript from Yahoo's and Google's content delivery networks (CDNs), and uses local alternatives in development mode so your site loads faster and looks right even when you don't have an Internet connection (eg, on an airplane).

Please see the comments in <tt>lib/local_cdn.rb</tt> for usage examples.

== Prerequisites

For YUI to be served locally, please install it at <tt>http://localhost/yui</tt>.

Copyright (c) 2009 Alex Reisner, released under the MIT license

Expand Prerequisites section of documentation.

= Local CDN

Local CDN simplifies the inclusion of external stylesheets and JavaScript from Yahoo's and Google's content delivery networks (CDNs), and uses local alternatives in development mode so your site loads faster and looks right even when you don't have an Internet connection (eg, on an airplane).

Please see the comments in <tt>lib/local_cdn.rb</tt> for usage examples.

== Prerequisites

For YUI to be served locally, please install it on your development machine. If you use this tag in your view:

  <%= yui_stylesheet_link_tag "2.7.0/build/base/base-min.css" %>

then the file must be available at:

  http:// localhost/yui/2.7.0/build/base/base-min.css

Basically, just create a +yui+ directory in your local web server's DocumentRoot and unzip the entire YUI package to it, renaming the package's root directory to its version number.

Copyright (c) 2009 Alex Reisner, released under the MIT license


= Imp

Imp is a simple framework for writing command-line applications, heavily
inspired by Merb and Sinatra.

== Dependencies

In order to keep Imp as portable as possible, dependencies are kept to a
minimum. Below is a list of gem dependencies for running Imp.

* *extlib* - The whole of extlib is not loaded; just a couple of helpers like
  class_inheritable_accessor and inflection. This may be a candidate for
  removal once the Big Rails Refactor is done, and ActiveSupport is more
  modular.

== Copyright

Copyright (c) 2009 Anthony Williams. See LICENSE for details.

Update readme with some actual information. :)

= Imp

Inspired by Merb and Sinatra, Imp is a Ruby framework which aims to simplify
development of command-line applications.

Imp allows you to define 'commands', much like you might define a controller
in a web framework, each of which contain actions. Imp then runs a particular
command and action depending on the command line arguments.

For example, assuming your executable is called 'mybin'...

    $ mybin find audio

... would be mapped to the 'audio' action on the 'Find' command. Also provided
is a handy DSL for parsing other command-line arguments. See the documentation
for Imp::Command for more information on both commands and arguments.

== Development Status

Imp is still in the early stages of development and is not yet ready for use.
Many of the core concepts (commands/argument parsing) are implemented, but
application generation and input/output are not yet completed.

== Tests

Tested on Ruby 1.8.6, 1.8.7, 1.9.1 and JRuby 1.2.0.

== Copyright

Copyright (c) 2009 Anthony Williams. See LICENSE for details.


= Prose

This project rocks and uses MIT-LICENSE.

Add basic info to readme

= Prose
== Project Aims
Prose is a general purpose CMS that assumes very little about how you want to use it. The goals of this project and related works are to create a very modular, a la carte type CMS framework using the current version of Rails.

The aim of this specific gem is to provide the core functionality.
The intent is to create several adaptors to plug into prose in order to provide additional capabilities.
All this means is that prose-core is the dumb container that holds the content and meta that makes up the site.  If, for example, you want to edit using Alhoa, create an adaptor.
This project rocks and uses MIT-LICENSE.


= desperados: A Ruby library for Ceph's Rados

Ceph is a distributed network storage and file system. It's based on a
reliable and scalable distributed object store calles RADOS.  More
about it here: http://ceph.newdream.net

Desperados is a Ruby wrapper for the C++ librados library, making
interacting with a Ceph cluster in Ruby very easy.

== Basic Example

	require 'rados'
  Rados::initialize

  pool = Rados::Pool.create("mypool")
  pool.write("mykey", "somedata")
  pool.read("mykey") == "somedata"

== Object Orientated Example

	require 'rados'
	Rados::initialize

	pool = Rados::Pool.create("mypool")
	o = pool.objects.new("mykey")
	o.write("Once upon")
	o.write(" a time")
	o.seek(0)
	o.read == "Once upon a time"
	o = pool.objects.find("mykey")
	o.seek(5)
	o.read == "upon a time"

== Configuration

librados will read your ceph.conf config file to discover your
cluster's monitors, so that needs to be available (usually in
./ceph.conf or /etc/ceph/ceph.conf)

== About

Author::  John Leach  (mailto:john@johnleach.co.uk)
Copyright:: Copyright (c) 2010, 2011 John Leach
License:: LGPL
Github:: http://github.com/johnl/desperados/tree/master

Fix formatting of object oriented example


= spore
    Spore is a specification for describing ReST API that can be parsed and used automatically by client implementations to communicate with the descibed API

== 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) 2010 Weborama. See LICENSE for details.

== Contributors
  - Alexis Sukrieh <sukria@sukria.net>
  - Hery Ramihajamalala hery@rails-royce.org>

Fix typo in mail format

= spore
    Spore is a specification for describing ReST API that can be parsed and used automatically by client implementations to communicate with the descibed API

== 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) 2010 Weborama. See LICENSE for details.

== Contributors
  - Alexis Sukrieh <sukria@sukria.net>
  - Hery Ramihajamalala <hery@rails-royce.org>


= foodtruck

Description goes here.

== Contributing to foodtruck

* 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.
* 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) 2014 Jose Ventura. See LICENSE.txt for
further details.

Add travis results to readme

{<img src="https://travis-ci.org/joventuraz/foodtruck.svg?branch=master" alt="Build Status" />}[https://travis-ci.org/joventuraz/foodtruck]
= foodtruck

Description goes here.

== Contributing to foodtruck

* 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.
* 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) 2014 Jose Ventura. See LICENSE.txt for
further details.