Search posterous

Search all posts and users. Type a name, type a favorite song title, whatever! See what comes up.
  

More posterous blogs

Holy Kaw!
Holy Kaw!
guykawasaki

ijustine
ijustine's posterous
ijustine | Justine Ezarik

garry
garry's posterous
garry | Garry Tan

The Official Posterous Posterous
The Official Posterous Posterous
Posterous

nicholaspatten
Nicholas Patten's Work/Life :)
nicholaspatten | Nicholas Patten

Steve
The Steve Rubel Lifestream
Steve | Steve Rubel

ReflectionOf.Me
ReflectionOf.Me
clementine osakin

TweetDeck's posterous
TweetDeck's posterous
tweetdeck pocketsteve richardbarley Iain

Leo
Leo LaPosterous
Leo | Leo Laporte

sachin
Sachin's Posterous
sachin | Sachin Agarwal

More recommended blogs »

Here are posterous posts filed under gems...

jayfallon says...
Nov 02, 2009

Apprise · Fingertips

Last friday Eloy and I participated in the Ruby en Rails Rails Rumble 2009, we had 8 hours to write an application which helped developers find out more information about the dependencies in their Rails application.

Our submission is called Apprise. Apprise is a tool to check gem dependencies and external repositories for newer versions of the currently installed ones in your Rails application.

To be more specific, it looks for three sources of dependencies. Git and Subversion externals in vendor/plugins and bundled Gems in the Gemfile. Checking for Gem dependencies is delegated to Bundler. If you don’t use Bundler to manage Gem dependencies you will still see outdated externals and submodules.

Outdated dependencies are listed and you can decide to update the externals, submodules or gems.

$ apprise                 
Outdated dependencies
 * forestwatcher (Subversion external)
 * risosu-san (Git submodule)
 * miso (Gem)

If you want to try it out you can easily install the gem and run the command in the root of your Rails application.

$ gem install apprise --source http://gemcutter.org

Unfortunately we did not win, but our patch for Bundler to list outdated gems was pulled by Yehuda Katz right after the competition.

via fngtps.com

Apprise is a tool to check gem dependencies and external repositories of the currently installed gems in your Rails application.

Filed under: Gems
Loading mentions Retweet
Comment (0) »

joshuaesc says...
Sep 29, 2009

Dr. Kelly on Providence

Dr. Kelly provided another great gem last night in his definition of providence: “By providence we mean what happens to you.”  Volumes could be written on the doctrine of God’s providence, yet Dr. Kelly distilled it in such a way that it was understandable and personally applicable.

Lord help us as teachers and preachers to know you so well that we can speak of you in the simplest terms.

For His Glory, Frank

The audio can be downloaded here.

Filed under: Gems
Loading mentions Retweet
Comment (0) »

garry says...
Dec 30, 2008

axonflux.posterous.com, a new posterous blog on Rails, scaling, and software engineering. First, upgrading to Rails 2.2.2

Hi there. There's a lot of magic in Rails, and as someone who works with it daily, it is absolutely amazing to see how valuable Google is to wading through the magic. I don't know what I would do without the help afforded me by the awesomeness of great Rails bloggers and the help of forums, so I figure here's my little contribution into the ether.

 

On plugins that broke
  • acts_as_paranoid ceased to work for me as of Rails 2.1.2. There was too much magic and it was really gumming up our MySQL indexes, so we killed it. One less where clause to worry about, and that's priceless when it comes to MySQL optimization.
  • xss_terminate needed an upgrade. no big deal there.
  • We use workling and starling in our stage/production environments, but workling and spawn in development. Connection pooling broke spawn, but I submitted a patch for Rails 2.2.2 so it's back in business again. Workling is the superb work of Rany Keddo of play/type -- great piece of software, by the way.
  • The rubyforge plugin continues to not play nicely with the AWS S3 gem, causing errors with 'tmp_dh_callback' -- but a simple plugin patch solves that quite elegantly.

 

Upgrading to RubyGems 1.3.1

You'd think that running gem update --system would do it, but you'd be wrong.

On ubuntu and OS X, you gotta run this:

sudo gem install rubygems-update
sudo update_rubygems

Thanks to intertwingly

 

Also, on freezing native gems...

I tried to be smart and do a rake gems:unpack and rake gems:unpack:dependencies, but unfortunately for me, rake gems:build fails on Ubuntu. It failed specifically on hpricot, eventmachine and json gems, all of which had native extensions.

I just dropped those into my config.gems instead, and made sure to run rake gems:install on the stage/production servers after deploy.

 

And a quick note on the importance of tests...

Every Rails update has significant impact on the rest of your app. Unit and integration tests are critical for being able to catch these bugs without resorting to manual testing... but that'll be a future blog post.

Filed under: gems
Loading mentions Retweet
Comment (0) »