The first article in a series where 'Working with Unix Processes' author Jesse Storimer implements a Unix shell in pure Ruby code.
Is Ruby Interpreted or Compiled?
Pat Shaughnessy returns with yet another great article diving into the world of Ruby intepreters and execution. This time he looks at the compilers in Rubinius and JRuby and what they're producing.
Rails Went Off The Rails: Why I'm …
- Giles Bowkett: Rails Went Off The Rails: Why I'm Rebuilding Archaeopteryx In CoffeeScript
- Merbist: Learning from Rails' failures
- Paul Gross's Blog: Untangle Domain and Persistence Logic with Curator
- Andrzej on Software: Rails is still cool
- Plataformatec Blog: My five favorite "hidden" features in Rails 3.2
- Life at the Speed of Green: callback_skipper for faster factories
Tasks are any command that can be run in your application or even the Unix shell.
For Rails, the convention is to set up rake tasks. To create your scheduled tasks in Rails, copy the code below into lib/tasks/scheduler.rake and customize it to fit your needs. desc "This task is called by the Heroku scheduler add-on" task :update_feed => :environment do puts "Updating feed..." NewsFeed.update puts "done." end
task :send_reminders => :environment …
- Trevor Turk: Links for 3-15-11
- A Fresh Cup: Double Shot #572
- Scout ~ The Blog: 5 Pillars of Rails Cluster Monitoring
- MySQL Performance Blog: MySQL caching methods and tips
- On the Path: Accounting for Time in a State-Based Workflow
- elc technologies - Blog : Ruby on Rails, iPhone, Flash, Agile, Interactive Design: Ruby Daemons and Angels
…The Shell Hater's Handbook , an introductory talk on UNIX shell programming for Ruby hackers given at GoGaRuCo 2010 . Alas, the post-conference wrap up magazine will not be published this year and so I'm making the essay available here instead.
Ruby, like most successful languages, was assembled from pieces of things that came before it: Smalltalk's consistent object system, Perl's practical syntax, UNIX's sensibilities. Not that it didn't …
- Trevor Turk: Links for 5-17-11
- A Rubyist Railstastic Adventure: AWK-ward Ruby
- Luigi Montanez: Ten Ruby Conferences (and Three Camps) in Eight Weeks
- has_many :through: GoGaRuCo 2010
- Mislav's blog: You're cuking it right
I asked around, and some people had the vague idea that there was a $PATH cache in Unix shells. Someone pointed me at this post about clearing the cache .
Sure enough, running hash -r fixed the output of which . I alerted Wayne of rvm to this problem, and he threw in a fix to rvm that cleared the cache when switching rvms. Momentarily, everything seemed fine.
Digging Further
I still didn't exactly understand how this condition could happen in the first place. …
- Phusion Corporate Blog: Ruby Enterprise Edition 1.8.7-2010.02 released
- Opscode Blog: Chef 0.9.0 and Ohai 0.5.6 Released
- Merbist: Ruby object allocation & why you should care
- Heroku: Rails 3 Beta 4 on Heroku
- Luke Redpath: Downloading iTunes finance reports into FreeAgent
- Envy Labs: No Callbacks, No Threads & Ruby 1.9
…framework on the next project, so I could learn more. And so, over the years I have explored all kinds of UNIX shell commands, scripting languages Tcl/Tk, web-development languages, low-level C++ and more.
PHP is really as much here to stay as it's ever been. Why do you think it has been so successful and long lived?
Zeev: I don't pretend to know the complete answer to that question, because at the end of the day, a lot of this has to do with dynamics that are too big to …
- Null is Love: PHP 5.3 Released
- Videos related to 'Ruby on Rails vs PHP - Commercial #3 of 9': PHP MVC Introduction - FUSE Model View Controller Framework
- Junior developer: Faster RubyGem deploys thanks to Jeremy Kemper
- Biodegradable Geek: Small Vim Shortcut for PHP Tags
- Videos related to 'Ruby on Rails vs PHP - Commercial #2 of 9': XAMPP - Make your Computer a Webserver: Apache, PHP, MySQL
- Viget.com Blogs: RubyConf 2009 Recap
Quite simple for anyone familiar with Unix shell scripting. A normal exit status of zero indicates success, anything else indicates a problem. I have also added the option of specifying the required test coverage number. When the other developers see how easy it is, it will naturally rise to 100%, no? namespace :test do ... desc 'Ensure that existing tests cover a required percentage of the code.' # task :coverage_minimum_met => 'test:coverage' do task …
- Litany Against Fear: Testing as Communication: Real-World Techniques Notes
- Viget.com Blogs: Continuous Deployment for Staging