fhwang

namespace :spec do
  namespace :units do
    desc "Run unit specs with PATTERN in the spec file name"
    RSpec::Core::RakeTask.new(:selective => "db:test:prepare") do |t|
      t.pattern = FileList["spec/**/*#{ENV['PATTERN']}*_spec.rb"].exclude("spec/integration/**/*_spec.rb")
    end
  end

  namespace :integration do
    desc "Run integration specs with PATTERN in the spec file name"

fnichol

A Common .ruby-version File For Ruby Projects

Background

I've been using this technique in most of my Ruby projects lately where Ruby versions are required:

• Create .rbenv-version containing the target Ruby using a definition name defined in ruby-build (example below). These strings are a proper subset of RVM Ruby string names so far...
• Create .rvmrc (with rvm --create --rvmrc "1.9.3@myapp") and edit the environment_id= line to fetch the Ruby version from .rbenv-version (example below).

Today I learned about another Ruby manager, rbfu, where the author is using a similar technique with .rbfu-version.

firedfox

const PHANTOM_FUNCTION_PREFIX = '/* PHANTOM_FUNCTION */';

var page = require('webpage').create();

page.onConsoleMessage = function(msg) {
    if (msg.indexOf(PHANTOM_FUNCTION_PREFIX) === 0) {
        eval('(' + msg + ')()');
    } else {
        console.log(msg);
    }

dblock

# inspired by https://github.com/rspec/rspec-core/pull/596
require 'rspec/core/formatters/base_formatter'

module RSpec
  module Core
    module Formatters
      class FailuresFormatter < BaseFormatter
        
        def dump_failures
          return if failed_examples.empty?

irae

{
  /*** Globals ***/
  // To ignore any custom global variables, enable the `predef` option and list
  // your variables within it.
  "predef": [
	  "exports",
	  "YUITest",
	  "YUI",
	  "YUI_config",
	  "YAHOO",

natritmeyer

NOTE: I've created a gem based on this: https://github.com/natritmeyer/yarjuf

---------

rspec my_spec.rb -r ./junit.rb -f JUnit -o results.xml

zspencer

#symlink gcc to a non-llvm version installed xCode's CLI tools

if [ -f /usr/bin/gcc-4.2 ]; then
  sudo rm /usr/bin/gcc
  sudo ln -s /usr/bin/gcc-4.2 /usr/bin/gcc

  sudo rm /usr/bin/cc
  sudo ln -s /usr/bin/gcc-4.2 /usr/bin/cc
fi

markrickert

#!/bin/bash

# Takes one parameter: a remote git repository URL.
#
# This is the stuff this script does:
#
# 1. Clones the repository
# 2. Fetches all remote branches
# 3. Compresses the folder
# 4. Deletes the cloned folder.

Blackshawk

In the comments from my last post and on Twitter I noticed a lot of people who had something to say about PHP. The comments were varied but they usally sounded something like this (sorry @ipetepete, I picked yours because it was the shortest).

...the little bits of soul from all of us who've had to work on, and or maintain large PHP applications. – ipetepete

In Pete's defense, he did go on to say that rest of the stack I was using was a "smorgasbord of awesome". Thanks, Pete. I agree!

I would, however, like to take a little time to correct a misperception in the developer community about PHP. I recently got into this same... discussion... with Jeff Atwood, and I seem to be running into it more and more. So here goes. Please bear with me as I cover a little history further on.

Pete, and everybody else, _you're exactly rig

matsuda

$ brew install openssl
==> Downloading http://openssl.org/source/openssl-1.0.1e.tar.gz
######################################################################## 100.0%
==> perl ./Configure --prefix=/usr/local/Cellar/openssl/1.0.1e --openssldir=/usr/local/etc/openssl zlib-dynamic shared darwin64-x86_64-cc
==> make
==> make test
==> make install MANDIR=/usr/local/Cellar/openssl/1.0.1e/share/man MANSUFFIX=ssl
==> Caveats
To install updated CA certs from Mozilla.org: