Badges Table For Github Readme

You can add the following table for your project’s Readme (known compatible with Github-flavored markdown). Just find-replace “pboling” with your github username, and find-replace the project name, in this case “rack-insight” with your project name. I will be adding badges here as I come across ones I want to add to my projects’ Readmes.

The result is something like this:

Project Rack Insight
gem name rack-insight
license MIT
moldiness Maintainer Status
version Gem Version
dependencies Dependency Status
code quality Code Climate
continuous integration Build Status
test coverage Coverage Status
homepage https://github.com/pboling/rack-insight
documentation http://rdoc.info/github/pboling/rack-insight/frames
author Peter Boling
Spread ~♡ⓛⓞⓥⓔ♡~ Endorse Me

Here is the code:

| Project                 |  Rack Insight   |
|------------------------ | --------------- |
| gem name                |  rack-insight   |
| license                 |  MIT            |
| moldiness               |  [![Maintainer Status](http://stillmaintained.com/pboling/rack-insight.png)](http://stillmaintained.com/pboling/rack-insight) |
| version                 |  [![Gem Version](https://badge.fury.io/rb/rack-insight.png)](http://badge.fury.io/rb/rack-insight) |
| dependencies            |  [![Dependency Status](https://gemnasium.com/pboling/rack-insight.png)](https://gemnasium.com/pboling/rack-insight) |
| code quality            |  [![Code Climate](https://codeclimate.com/github/pboling/rack-insight.png)](https://codeclimate.com/github/pboling/rack-insight) |
| continuous integration  |  [![Build Status](https://secure.travis-ci.org/pboling/rack-insight.png?branch=master)](https://travis-ci.org/pboling/rack-insight) |
| test coverage           |  [![Coverage Status](https://coveralls.io/repos/pboling/rack-insight/badge.png)](https://coveralls.io/r/pboling/rack-insight) |
| homepage                |  [https://github.com/pboling/rack-insight][homepage] |
| documentation           |  [http://rdoc.info/github/pboling/rack-insight/frames][documentation] |
| author                  |  [Peter Boling](https://coderbits.com/pboling) |
| Spread ~♡ⓛⓞⓥⓔ♡~      |  [![Endorse Me](https://api.coderwall.com/pboling/endorsecount.png)](http://coderwall.com/pboling) |

[documentation]: http://rdoc.info/github/pboling/rack-insight/frames
[homepage]: https://github.com/pboling/rack-insight
Fork me on GitHub

Contributing Section in OSS Readmes

I am going to be working on improving this copy on my repos soon.  Posting the default version here as a baseline.  This will be evolving.

## Contributing

1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am ‘Added some feature’`)
4. Push to the branch (`git push origin my-new-feature`)
5. Make sure to add tests for it. This is important so I don’t break it in a future version unintentionally.
6. Create new Pull Request

Versioning Section in OSS Readmes

Inspiration comes from the twitter gem’s readme. I have removed the bit about yanking gems, because cases where that is appropriate should be, and are, extremely rare.

Markdown

## Versioning

This library aims to adhere to [Semantic Versioning 2.0.0][semver].
Violations of this scheme should be reported as bugs. Specifically, 
if a minor or patch version is released that breaks backward 
compatibility, a new version should be immediately released that
restores compatibility. Breaking changes to the public API will 
only be introduced with new major versions.
As a result of this policy, you can (and should) specify a 
dependency on this gem using the [Pessimistic Version Constraint][pvc] with two digits of precision. 
For example:
    spec.add_dependency 'twitter', '~> 4.0'

[semver]: http://semver.org/
[pvc]: http://docs.rubygems.org/read/chapter/16#page74

RDOC

== Versioning
This library aims to adhere to {Semantic Versioning 2.0.0}[http://semver.org/].
Violations of this scheme should be reported as bugs. Specifically, 
if a minor or patch version is released that breaks backward 
compatibility, a new version should be immediately released that
restores compatibility. Breaking changes to the public API will 
only be introduced with new major versions.
As a result of this policy, you can (and should) specify a 
dependency on this gem using the {Pessimistic Version Constraint}[http://docs.rubygems.org/read/chapter/16#page74] with two digits of precision.
For example:
    spec.add_dependency 'twitter', '~> 4.0'

CookieOverflow in Rails 4

Rails 4 encrypted cookie store is awesome:

[sourcecode lang="ruby"]
MyApp::Application.config.session_store :encrypted_cookie_store …
[/sourcecode]

I switched! And then I was immediately hit with cold bucket of water right after a facebook / devise / oauth:

    ActionDispatch::Cookies::CookieOverflow

So if you were just under 4kb before you will split your britches! Switch to active record session store. First comment out the :encrypted_cookie_store line in config/initializers/session_store.rb.

Uncomment config/initializers/session_store.rb to:

[sourcecode lang="ruby"]
    MyApp::Application.config.session_store :active_record_store
[/sourcecode]

Add this to your gemfile:

[sourcecode lang="ruby"]
gem ‘activerecord-session_store’, github: ‘rails/activerecord-session_store’
[/sourcecode]

Then install:

[sourcecode lang="bash"]
bundle install
[/sourcecode]

Then create the migration:

[sourcecode lang="bash"]
bundle exec rails g active_record:session_migration
[/sourcecode]

Then run migrations:

[sourcecode lang="bash"]
bundle exec rake db:migrate
RAILS_ENV=test bundle exec rake db:migrate
[/sourcecode]

Then restart the app server!

Current Projects

I needed to create an order of importance to my current gems and jQuery libraries, and thought it may be useful to post it publicly.  I was just faced with a decision about which state machine to add to a new project, and had some difficulty determining which were still alive.  So this list may serve some purpose for someone wondering how alive my projects are.  Any of my projects which are not in this list are dead to me (for now).

Here is the ordered, prioritized, list:

  1. pboling/rack-insight
  2. pboling/flag_shih_tzu
  3. pboling/sanitize_email
  4. pboling/jquery.cacheableFlash
  5. pivotal/cacheable-flash
  6. pboling/stackable_flash
  7. pboling/dry_views
  8. pboling/jquery.environment
  9. mbleigh/subdomain-fu
  10. pboling/csv_pirate
  11. pboling/capistrano_mailer
  12. pboling/jquery.ellipsis

 

 

 

 

 

Rails Bling Lives!

Rails Bling will be the homepage for my Open Source efforts.  I will post about my efforts here, especially when I release new versions of software.

On the name: Bling is a pun, since my last name is Boling, and Rails is my passion and expertise!

On myself: Fooby-Ru Wizard

[sourcecode lang="ruby"]
class RailsBling # PORO
def first
‘Post’
end
def image
‘Sexy’
end
end
[/sourcecode]