byplayer

INSTALL
=======

$ gem install rspec

RSPEC-RAILS
===========

  RAILS-3
  =======

flavio

#!/usr/bin/env ruby

require 'rubygems'
require 'bundler'
require 'fileutils'
require 'net/http'
require 'net/https'
require 'uri'

TMP_DIR = "/tmp/gems"

marktheunissen

This playbook has been removed as it is now very outdated.

orta

# Artsy Editorial
#
# Get Page stats from google analytics

GA = require('googleanalytics')
util = require('util')
require('date-utils');        
   
module.exports = (robot) ->
  robot.hear /stats (.*)http:\/\/artsy.net\/(.*)/i, (msg) ->

Jared314

;[org.jodd/jodd-lagarto "3.4.2"]
;(:import [jodd.csselly CSSelly CssSelector Combinator Selector$Type])

(defn format-attr-selector [x]
      (case (.getName x)
            "id" (str "#" (.getValue x))
            "class" (str "." (.getValue x))
            ""))
  
(defn format-selector [x]

djangofan

// This is the official Selenium documention endorsed method of waiting for elements.
// This method is ineffective because it still suffers from
// the stale element exception.
public static void clickByLocator ( final By locator ) {
  WebElement myDynamicElement = ( new WebDriverWait(driver, 10))
    .until( ExpectedConditions.presenceOfElementLocated( locator ) );
  myDynamicElement.click();
}

markhibberd

Installation

FreeBSD

portmaster irc/irssi
portmaster irc/irssi-xmpp

OS X

brew install irssi

jpetazzo

# this forces dpkg not to call sync() after package extraction and speeds up install
RUN echo "force-unsafe-io" > /etc/dpkg/dpkg.cfg.d/02apt-speedup
# we don't need and apt cache in a container
RUN echo "Acquire::http {No-Cache=True;};" > /etc/apt/apt.conf.d/no-cache

crosbymichael

Links - Spec

Links are a way of expressing a relationship between one container and another. When you link a container, you create a parent/child relationship between the two. As a side effect links also allow you to name containers and reference them by name. Containers can be references by more than one name.

Breaking changes

This the new link feature we will be disabling intercontainer communication by default. Containers will not be able to communicate with each other over the docker0 bridge without having a link to that container. Even with a link, a parent can only communicate to the ports exposed by the child and nothing more.

Initially links will be expressed by injecting the child's data into the parent's environment accessible via namespaced variables:

tmatilai

# URI of the local (caching) HTTP proxy
LOCAL_HTTP_PROXY = 'http://192.168.33.200:8123'

# Configures vagrant-cachier and vagrant-proxyconf.
# Should be called only on "local machine" providers.
def configure_caching(config)
  if Vagrant.has_plugin?('vagrant-cachier')
    config.cache.enable_nfs = true
    config.cache.enable :gem
    config.cache.enable :npm