<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for rubypond</title><link>http://disqus.com/by/rubypond/</link><description></description><atom:link href="http://disqus.com/rubypond/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Wed, 21 Oct 2015 18:12:55 -0000</lastBuildDate><item><title>Re: Heroku is no longer the hobbyist's friend</title><link>https://blog.jalada.co.uk/heroku-is-no-longer-the-hobbyists-friend/#comment-2319900726</link><description>&lt;p&gt;So you get free SSL, at &lt;a href="https://your-app-name.herokuapp.com/" rel="nofollow noopener" target="_blank" title="https://your-app-name.herokuapp.com/"&gt;https://your-app-name.herok...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;What you're asking for is to have SSL on your own branded domain. Is it really a "hobby" at that point?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Gillen</dc:creator><pubDate>Wed, 21 Oct 2015 18:12:55 -0000</pubDate></item><item><title>Re: Heroku is no longer the hobbyist's friend</title><link>https://blog.jalada.co.uk/heroku-is-no-longer-the-hobbyists-friend/#comment-2319897625</link><description>&lt;p&gt;Yeah, I think people often make the mistake of comparing Heroku costs (which include some amounts of automation/fail-over/backups, especially on DBs) with just the raw infrastructure costs elsewhere. They then assume their own time is worth nothing, that they won't have to spend a single minute doing any of this stuff themselves, or that it magically takes care of itself.&lt;/p&gt;&lt;p&gt;SSL is definitely a sting here. Kinda ironically though the ExpeditedSSL integration is one of the things (along with Postgres) that keeps some of my apps there. $45/mo to never have to worry about a a certificate accidentally expiring, along with quarterly cert rotation and the someone else making sure it's up-to-date with the latest best practices is a simple decision imo. I've only so many hours in the day to keep track of things.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Gillen</dc:creator><pubDate>Wed, 21 Oct 2015 18:10:37 -0000</pubDate></item><item><title>Re: Heroku is no longer the hobbyist's friend</title><link>https://blog.jalada.co.uk/heroku-is-no-longer-the-hobbyists-friend/#comment-2318833941</link><description>&lt;p&gt;On the SSL point, the reason for the cost is partly to do with the broken state of TLS/SSL and using it in a multi-tenant environment. When you add it you might have noticed you get a new CNAME to point your DNS to. That's because a whole new dedicated Amazon ELB is spun up just for you, so that you can have your SSL certificate installed on it and it can then manage SSL termination for you. Last time I did the math on that I think it cost somewhere between $18 and $19 a month (depending on the number of hours/days in the month). Add in bandwidth costs and I suspect Heroku is making a loss on them, before you factor in their own ops and support overhead for providing them. I'm still unhappy that it costs so much, but I also understand why it isn't free. They do actually give you a free option, just that it's on a Heroku branded domain.&lt;/p&gt;&lt;p&gt;As for the Cloudflare type approach, that creates a whole world of different problems. If you find your SSL terminating on the same instances as some questionable neighbor you might find a number of people can't access your site at all. Lots of jurisdictions, or just over-zealous ISPs, actively filter the content the users can access. And they often do it by IP address, which is how your site gets caught in the mix. While I lived in the UK I think that included every mobile network, and it's a lot of ISPs back here.&lt;/p&gt;&lt;p&gt;We disagree on postgres too :) Spinning up a database is just the tip of the iceberg. The real cost comes from preventing things from going wrong, and resolving them if they do. I'm happy to pay $50/mo for automated backups, multi-site storage of write-ahead-logs, automated monitoring, automated recover/failover if an instance goes down, rollbacks, ability to fork/follow, and dataclips. Setting up and maintaining all of that for myself would easily take more than 30min/month. So it's way cheaper to let Heroku do it.&lt;/p&gt;&lt;p&gt;I completely agree with everything else though. Chat bots have to move. Other little trivial things too. I'd been meaning to play more with CoreOS and Kubernetes for another app I had that couldn't run on Heroku. Between that or &lt;a href="http://Convox.io" rel="nofollow noopener" target="_blank" title="Convox.io"&gt;Convox.io&lt;/a&gt; I suspect I'll have a single platform to run all of my apps, big or small&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Gillen</dc:creator><pubDate>Wed, 21 Oct 2015 07:32:17 -0000</pubDate></item><item><title>Re: I quit the techÂ industry</title><link>https://eev.ee/blog/2015/06/09/i-quit-the-tech-industry/#comment-2071679268</link><description>&lt;p&gt;Great and timely perspective. Today I've just ticked over 12 months since I left my tech job, most of my time since has been spent with my family and enjoying watching our son grow. It's really helped me come to terms with what's important and how (in)significant most of what we do in a given work day really is, which makes the anguish it often causes all the more pointless. I'm going to start my own business soon and finding a way to provide true work/life balance is going to be one of the most important things for me to instill culturally. Not the lip-service fake balance I've seen so many tech companies where what really happens is the lines between work and non-work just become blurred. I wish you all the best for whatever comes next and hope that the period in between is as restorative for you as it has been for me.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Gillen</dc:creator><pubDate>Wed, 10 Jun 2015 08:42:15 -0000</pubDate></item><item><title>Re: Add-ons for Production Apps</title><link>https://blog.heroku.com/archives/2013/7/8/addons_production_apps#comment-966642652</link><description>&lt;p&gt;I can second what Daniel has said. As Heroku Postgres has your hot data in RAM it's pretty fast, and has JSON support in the form of hstore. A big benefit of a dedicated caching solution is the automatic expiry so you don't need a separate process to go through and do the cleanup.&lt;/p&gt;&lt;p&gt;On the &lt;a href="http://addons.heroku.com" rel="nofollow noopener" target="_blank" title="addons.heroku.com"&gt;addons.heroku.com&lt;/a&gt; app we're running a cache in front to store the rendered output of the most frequently accessed pages. In many cases it can avoid a DB hit completely, and we get some failover by having two accessible proxies for the cache. If that fails or hits a timeout, then the page is still rendered just a bit more slow from n queries in the database.&lt;/p&gt;&lt;p&gt;If it's possible to easily replicate your use case I'd consider deploying an example to a staging app and then running a load test against different implementations using something like &lt;a href="http://Blitz.io" rel="nofollow noopener" target="_blank" title="Blitz.io"&gt;Blitz.io&lt;/a&gt; (&lt;a href="https://addons.heroku.com/blitz)" rel="nofollow noopener" target="_blank" title="https://addons.heroku.com/blitz)"&gt;https://addons.heroku.com/b...&lt;/a&gt; to know which one works best for you.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Gillen</dc:creator><pubDate>Thu, 18 Jul 2013 02:27:07 -0000</pubDate></item><item><title>Re: Why You Need a Git Pre-Commit Hook and Why Most Are Wrong</title><link>http://tech.yipit.com/2011/11/16/183772396/#comment-364976166</link><description>&lt;p&gt;Great post. I think part of the reason why a lot of pre-commit hook examples check the whole project is because there is no way to enforce certain hooks as mandatory across the team. So in the example above JShint would only be run on the files I touched.&lt;/p&gt;&lt;p&gt;At least that's why I do it. Trust no one! ;)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Gillen</dc:creator><pubDate>Wed, 16 Nov 2011 14:33:13 -0000</pubDate></item><item><title>Re: 13 Things You Must Do Every Week As A Startup CEO</title><link>http://betashop.com/post/4367407080#comment-178596296</link><description>&lt;p&gt;My only criticism, why should this advice be limited to "startup" CEOs? I wish every CEO I'd encountered considered this every day.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Gillen</dc:creator><pubDate>Tue, 05 Apr 2011 13:08:43 -0000</pubDate></item><item><title>Re: 37signals vs Zappos</title><link>http://blog.teamtreehouse.com/37signals-vs-zappos#comment-623102671</link><description>&lt;p&gt;I spent the first half of my career setting up contact centres in numerous countries, the latter half working in something more like start-up environments. So hopefully I've got some perspective on the reason for the differences between both.&lt;/p&gt;&lt;p&gt;Firstly Zappos. It's no doubt a great company to work for, the contact centres I'd setup were regularly voted the best places to work which is highly usual for that sector. They're usually drab and lifeless places, where people are essentially chained to their desk by a headset. Toilet breaks often need to be cleared with a manager first, you need to literally clock in and out each day, and to top it all off most of your time is spent trying to calm down angry people who are calling to complain about something. The staff really are fighting on the front line and they have a hell of a task to stay happy and motivated about what they do because at the end of the day, it's a pretty sucky job. The solution to that? Make everything else fun. The workplace and the surroundings have to work as a distraction from the other negative impacts on their job. Some autonomy to decorate their environment creates an outlet for expression in a role that is otherwise heavily regimented and scripted.&lt;/p&gt;&lt;p&gt;Compare that to the average life of a developer, most of us actively love the work we do. Writing code, producing something people get to use, and the sense of accomplishment that comes with it. Jason is on record as saying (paraphrasing here) that interruptions are rude, you're basically saying whatever I want is more important than whatever you're doing. Mental state and flow is important to a developer, distractions are preferable kept to a minimum, and that includes the environmental ones. It's no surprise that their office reflects that, and I think it does so for good reason.&lt;/p&gt;&lt;p&gt;I think it's just two companies servicing everyones innate desire to be just a little bit creative in the best way they can. For one it's in the environment they create, the other it's the work they produce.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Gillen</dc:creator><pubDate>Fri, 11 Feb 2011 12:13:00 -0000</pubDate></item><item><title>Re: 37signals vs Zappos</title><link>http://thinkvitamin.com/web-industry/37signals-vs-zappos/#comment-144683673</link><description>&lt;p&gt;I spent the first half of my career setting up contact centres in numerous countries, the latter half working in something more like start-up environments. So hopefully I've got some perspective on the reason for the differences between both.&lt;/p&gt;&lt;p&gt;Firstly Zappos. It's no doubt a great company to work for, the contact centres I'd setup were regularly voted the best places to work which is highly usual for that sector. They're usually drab and lifeless places, where people are essentially chained to their desk by a headset. Toilet breaks often need to be cleared with a manager first, you need to literally clock in and out each day, and to top it all off most of your time is spent trying to calm down angry people who are calling to complain about something. The staff really are fighting on the front line and they have a hell of a task to stay happy and motivated about what they do because at the end of the day, it's a pretty sucky job. The solution to that? Make everything else fun. The workplace and the surroundings have to work as a distraction from the other negative impacts on their job. Some autonomy to decorate their environment creates an outlet for expression in a role that is otherwise heavily regimented and scripted.&lt;/p&gt;&lt;p&gt;Compare that to the average life of a developer, most of us actively love the work we do. Writing code, producing something people get to use, and the sense of accomplishment that comes with it. Jason is on record as saying (paraphrasing here) that interruptions are rude, you're basically saying whatever I want is more important than whatever you're doing. Mental state and flow is important to a developer, distractions are preferable kept to a minimum, and that includes the environmental ones. It's no surprise that their office reflects that, and I think it does so for good reason.&lt;/p&gt;&lt;p&gt;I think it's just two companies servicing everyones innate desire to be just a little bit creative in the best way they can. For one it's in the environment they create, the other it's the work they produce.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Gillen</dc:creator><pubDate>Fri, 11 Feb 2011 07:13:11 -0000</pubDate></item><item><title>Re: Story Point Algebra</title><link>http://ryandotsmith.heroku.com/2011/02/story-point-algebra.html#comment-143942089</link><description>&lt;p&gt;I've always found the Fib estimations a bit weird for precisely that reason. Not because it's not a good way of estimating complexity (I'm indifferent on that) but because, as you intimate,  when you stand back objectively ask "what are we trying to do here?" you're wanting to know how long it will take to complete and how much work you can schedule.&lt;/p&gt;&lt;p&gt;The places I've worked where the points reflected this the most consistently have been where estimation was done in days. 0.5 day, 1 day, 2 days, 2.5 days at the most. Anything beyond that and you've probably not broken the story down into the simplest thing to get the job done (improvements can be a later story for a subsequent iteration). Then just map that effort to some arbitrary points system (1, 2, 4, 5) so that you remove yourself from explaining load factor to clients, they just get to schedule a set number of points each iteration.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Gillen</dc:creator><pubDate>Thu, 10 Feb 2011 03:35:44 -0000</pubDate></item><item><title>Re: Cucumber vs. Steak</title><link>http://iain.nl/2011/01/cucumber-vs-steak/#comment-138082887</link><description>&lt;p&gt;It *could* help people separate problem/solution, but most don't. It's just as easy to do it wrong with Cucumber and as you've said the example web steps actually lead you the wrong way and as a result many people do it wrong.&lt;/p&gt;&lt;p&gt;It takes conscious effort from the developer to separate the two issues, and at that point you could expend the conscious effort in making sure your tests in any framework are readable and testing the right things.&lt;/p&gt;&lt;p&gt;And so I think you've succinctly identified my main issue with Cucumber, and it's not really with Cucumber at all. It's that people seem to think using it and saying "BDD" magically means you've fixed what was essentially a process or communication problem. You've still got that problem unless you've changed your approach, you're just using a different tool to keep doing it wrong.&lt;/p&gt;&lt;p&gt;Personally I stick with index cards for the plain English stuff, it's easier for me to shove them in front of the client and go through them that to convince them to look at the output of a test run somewhere. They're happy to take my word on whether the card is "green".&lt;/p&gt;&lt;p&gt;EDIT: Forgot to mention, I thought it was a great summary of the real pros/cons (as opposed to the usual feature comparisons). I'm not convinced Steak is any better at solving this problem.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Gillen</dc:creator><pubDate>Tue, 01 Feb 2011 04:45:04 -0000</pubDate></item><item><title>Re: Flash Ad: BMW Burns Logo onto Cinema-Goers&amp;#8217; Eyes</title><link>http://www.wired.com/gadgetlab/2010/12/flash-ad-bmw-burns-logo-onto-cinema-goers-eyes/#comment-112774509</link><description>&lt;p&gt;Living in Europe (does Australia qualify as "Asia" these days?) and going to the cinema on average once a week I can anecdotally report that mobile usage once inside is incredibly low, maybe one person every 3-4 visits but only ever during the non-Movie advertisements even then.&lt;/p&gt;&lt;p&gt;High mobile usage in a country does not automatically imply a decline in decency standards. Cinemas, theatres, etc. are typically places where actions that distract other patrons are frowned upon. I'd be saddened if that changed.&lt;/p&gt;&lt;p&gt;Drawing a false correlation from data doesn't protect someone from also looking arrogant and naive.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Gillen</dc:creator><pubDate>Thu, 16 Dec 2010 04:15:12 -0000</pubDate></item><item><title>Re: Postmodern - Mining RubyGems from Ore</title><link>http://postmodern.github.com/2010/10/25/mining-rubygems-from-ore.html#comment-111510645</link><description>&lt;p&gt;A bit late to this conversation, stumbled this way from a post postmodern made about Ore on the ruby learning blog.&lt;/p&gt;&lt;p&gt;I agree with Ryan, the main problem is rubygems should be doing most of what these tools do. Until that day I like the look of Ore, certainly seems like one of the better gem-cutting tools so thanks for pointing it out. I'll definitely take a deeper look.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Gillen</dc:creator><pubDate>Tue, 14 Dec 2010 07:07:28 -0000</pubDate></item><item><title>Re: PayPal+VP+On+Blocking+WikiLeaks%3A+State+Department+Said+It+Was%26nbsp%3BIllegal</title><link>http://techcrunch.com/2010/12/08/paypal-wikileaks/#comment-108717095</link><description>&lt;p&gt;Account closed, feels good to be done with this horrible company.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Gillen</dc:creator><pubDate>Wed, 08 Dec 2010 12:01:55 -0000</pubDate></item><item><title>Re: Should Nesta be a gem? - Nesta, a Ruby CMS</title><link>http://nestacms.com/blog/converting-nesta-to-a-gem#comment-108655426</link><description>&lt;p&gt;+1&lt;/p&gt;&lt;p&gt;As you said, would make mounting it in Rails much easier than it is at the moment. Plus it would reduce a lot of duplication on my server as I have a nesta checkout for each site I host, I could just have 1 system gem instead.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Gillen</dc:creator><pubDate>Wed, 08 Dec 2010 09:07:58 -0000</pubDate></item><item><title>Re: Running background jobs with resque - /dev/mull</title><link>http://www.devmull.net/articles/resque-implementation-walkthrough#comment-95026155</link><description>&lt;p&gt;You've been giving examples using MetricsList but the ResqueJob implementation is for MetricsUnsavedList, is that by accident or is it indeed a different class to the one that has perform/while_updating_job_status?&lt;/p&gt;&lt;p&gt;The only way you can return the class name easier is to drop the self., as it's implicit given you're in a class method. On that note, the @job assignment is assigning to a class variable given the scope you're in. Running self.while_updating_job_status twice in the same ruby process will have the second call replace the assignment from the first which is almost certainly not what you want as it will create a right mess and update the incorrect records should two jobs be checked concurrently.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Gillen</dc:creator><pubDate>Mon, 08 Nov 2010 05:48:29 -0000</pubDate></item><item><title>Re: Our Git Workflow: Private Development, Public Releases - Braintree</title><link>https://www.braintreepayments.com/braintrust/our-git-workflow#comment-69404734</link><description>&lt;p&gt;I have to agree with Travis and Henrik here, and I don't buy the "feel that topic branches generate too much clutter". Branching in git is so quick and trivial that I'm always a little confused when people don't take advantage of it.&lt;br&gt;&lt;br&gt;Given that within git a branch, tag, and pretty much anything else is ultimately just a SHA pointer to a commit you may as well just do your development on master, rebase --interactive to squash your commits, and then tag whatever you release when you push to origin. Your 3 branches are just pointers to a specific commit SHA, 2 of them to the same SHA that you tagged, and one of those is only there so you can do a squash (which you can do with rebase).&lt;/p&gt;&lt;p&gt;I'm not advocating that approach though, I prefer to see a full commit history so if there is a particular change I'd like to pull in myself for whatever reason it's much easier to cherry-pick rather than delving through a massive diff.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Gillen</dc:creator><pubDate>Tue, 17 Aug 2010 16:00:53 -0000</pubDate></item><item><title>Re: 9 Ruby on Rails Backup Solutions</title><link>http://storecrowd.com/blog/rails-backups/#comment-41228937</link><description>&lt;p&gt;I've got one that I rolled myself, I've been meaning to package it up as a gem and make it public. Will try and do that in the next couple of days.&lt;/p&gt;&lt;p&gt;Watch &lt;a href="http://rubypond.com/blog/devops" rel="nofollow noopener" target="_blank" title="http://rubypond.com/blog/devops"&gt;http://rubypond.com/blog/de...&lt;/a&gt; for a post on it&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Gillen</dc:creator><pubDate>Tue, 23 Mar 2010 13:05:39 -0000</pubDate></item><item><title>Re: Nesta on Heroku - VorpalCode</title><link>http://vorpalcode.com/nesta-on-heroku#comment-32713632</link><description>&lt;p&gt;I've been using nesta too lately and it's been great; I've also opted for keeping the content in the same git repo. As a result, each nesta site is now just a separate branch off master so I can pull changes from Graham's github upstream and then easily merge them into each site when I need to. It's made managing multiple sites really simple, I get the benefit of a consistent CMS/framework without having to restrict every site to follow the same structure entirely.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Gillen</dc:creator><pubDate>Fri, 05 Feb 2010 04:04:01 -0000</pubDate></item><item><title>Re: JRuby, and why bouncers are assholes | Ruby Pond</title><link>http://rubypond.com/articles/2009/07/30/jruby-and-why-bouncers-are-assholes/#comment-32018957</link><description>&lt;p&gt;one more test&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Gillen</dc:creator><pubDate>Fri, 29 Jan 2010 04:26:24 -0000</pubDate></item><item><title>Re: JRuby, and why bouncers are assholes | Ruby Pond</title><link>http://rubypond.com/articles/2009/07/30/jruby-and-why-bouncers-are-assholes/#comment-32018952</link><description>&lt;p&gt;testing another comment&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Gillen</dc:creator><pubDate>Fri, 29 Jan 2010 04:26:10 -0000</pubDate></item><item><title>Re: Rails Underground - Day 1 | Ruby Pond</title><link>http://rubypond.com/articles/2009/07/24/rails-underground---day-1/#comment-32018946</link><description>&lt;p&gt;testing comments&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Gillen</dc:creator><pubDate>Fri, 29 Jan 2010 04:25:42 -0000</pubDate></item><item><title>Re: Using rspec have_tag</title><link>http://rubypond.com/articles/2008/03/31/using-rspec-have_tag/#comment-30034244</link><description>&lt;p&gt;Seems fine now, there's an ongoing problem with the code formatting lib I'm using in Radiant, I'm in the process of porting over to something else.&lt;/p&gt;&lt;p&gt;I love the idea of forcing a login to see the code though ;)&lt;/p&gt;&lt;p&gt;Glenn&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Gillen</dc:creator><pubDate>Sat, 16 Jan 2010 05:42:26 -0000</pubDate></item><item><title>Re: scRUBYt! Gets Plugins! | Ruby Pond</title><link>http://rubypond.com/articles/2009/01/16/scrubyt-gets-plugins/#comment-19479640</link><description>&lt;p&gt;Rup,&lt;/p&gt;&lt;p&gt;We've not made an official switch to skimr becoming the main and&lt;br&gt;stable branch purely because we don't have a viable replacement for&lt;br&gt;scraping sites with AJAX (the current Firewatir integration is a bit&lt;br&gt;gnarly and not as reliable as we'd like).&lt;/p&gt;&lt;p&gt;I'll be looking to integrate with celerity to allow us to to headless&lt;br&gt;javascript scraping, once that's done skimr will finally become the&lt;br&gt;production release and available as a gem. Until then you need to&lt;br&gt;clone the git repo, switch to the skimr branch, and then include the&lt;br&gt;checkout in your file:&lt;/p&gt;&lt;p&gt;git clone &lt;a href="git://github.com/scrubber/scrubyt.git" rel="nofollow noopener" target="_blank" title="git://github.com/scrubber/scrubyt.git"&gt;git://github.com/scrubber/s...&lt;/a&gt;&lt;br&gt;cd scrubyt&lt;br&gt;git fetch&lt;br&gt;git checkout -b skimr origin/skimr&lt;/p&gt;&lt;p&gt;Then in your project:&lt;/p&gt;&lt;p&gt;base_path = "/path/to/checkout"&lt;br&gt;require "#{base_path}/lib/scrubyt"&lt;/p&gt;&lt;p&gt;Hope that helps. If not let me know,&lt;/p&gt;&lt;p&gt;Glenn&lt;/p&gt;&lt;p&gt;2009/10/7 Disqus &amp;lt;&amp;gt;:&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Gillen</dc:creator><pubDate>Thu, 08 Oct 2009 01:51:47 -0000</pubDate></item><item><title>Re: Web Spidering and Data Extraction with scRUBYt! | Ruby Pond</title><link>http://rubypond.com/articles/2008/12/09/web-spidering-and-data-extraction-with-scrubyt/#comment-19479470</link><description>&lt;p&gt;Skimr has different dependencies than the current stable release of&lt;br&gt;scrubyt. It actually requires far fewer external libs and just one&lt;br&gt;different one, Nokogiri instead of Hpricot.&lt;/p&gt;&lt;p&gt;I've a shiny new MBP arriving this week and I'm going to try get away&lt;br&gt;with ONLY running ruby 1.9 on it, so any bug will hopefully be solved&lt;br&gt;shortly. I'll also be tackling full jruby support if we can.&lt;/p&gt;&lt;p&gt;Glenn&lt;/p&gt;&lt;p&gt;2009/10/7 Disqus &amp;lt;&amp;gt;:&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Glenn Gillen</dc:creator><pubDate>Thu, 08 Oct 2009 01:44:32 -0000</pubDate></item></channel></rss>