Contributing Section in OSS Readmes

January 19, 2013 by peter.boling

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

January 8, 2013 by peter.boling

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

January 8, 2013 by peter.boling

Rails 4 encrypted cookie store is awesome:

    MyApp::Application.config.session_store :encrypted_cookie_store ...

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:

    MyApp::Application.config.session_store :active_record_store

Add this to your gemfile:

gem 'activerecord-session_store', github: 'rails/activerecord-session_store'

Then install:

bundle install

Then create the migration:

bundle exec rails g active_record:session_migration

Then run migrations:

bundle exec rake db:migrate
RAILS_ENV=test bundle exec rake db:migrate

Then restart the app server!

Current Projects

December 20, 2012 by peter.boling

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:

Rails Bling Lives!

July 2, 2012 by peter.boling

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:

class RailsBling # PORO
  def first
    'Post'
  end
  def image
    'Sexy'
  end
end