enkessler

require 'fileutils'
require 'cucumber_analytics'
require 'cuke_modeler'
require 'cql'
require 'cql/model_dsl'


# Project structure setup
your_location_here = "#{File.dirname(__FILE__)}/.."
feature_directory = "#{your_location_here}/features"

avdi

Open3.pipeline_r(
  %W[xmllint --xinclude --xmlout #{spine_file}],
  # In order to clean up extraneous namespace declarations we need a second
  # xmllint process
  %W[xmllint --format --nsclean --xmlout -]) do |output, wait_thr|
  open(codex_file, 'w') do |f|
    IO.copy_stream(output, f)
  end
end

sw1nn

(ns ratelimit
  "Implement rate limiting using a token bucket"
  (:require [clojure.core.async :as async :refer [<!! >! alts! go chan dropping-buffer close! timeout]]))

(defprotocol TokenBucket
  (take-token [this])
  (release [this]))

(defn- ->period-ms [p]
  (if (keyword? p)

sstephenson

Simple file/stream encryption using OpenSSL

Create and store a 512-byte random encryption key named secret:

$ mkkey secret

Encrypt the contents of file with the secret key and write it to file.enc:

$ encrypt secret < file > file.enc

SzymonPobiega

If you have two days to learn the very basics of modelling, Domain-Driven Design, CQRS and Event Sourcing, here's what you should do:

In the evenings read the [Domain-Driven Design Quickly Minibook]{http://www.infoq.com/minibooks/domain-driven-design-quickly}. During the day watch following great videos (in this order):

1. Eric Evans' [What I've learned about DDD since the book]{http://www.infoq.com/presentations/ddd-eric-evans}
2. Eric Evans' [Strategic Design - Responsibility Traps]{http://www.infoq.com/presentations/design-strategic-eric-evans}
3. Udi Dahan's [Avoid a Failed SOA: Business & Autonomous Components to the Rescue]{http://www.infoq.com/presentations/SOA-Business-Autonomous-Components}
4. Udi Dahan's [Command-Query Responsibility Segregation]{http://www.infoq.com/presentations/Command-Query-Responsibility-Segregation}
5. Greg Young's [Unshackle Your Domain]{http://www.infoq.com/presentations/greg-young-unshackle-qcon08}
6. Eric Evans' [Acknowledging CAP at the Root -- in the Domain Model]{ht

mislav

The reason why you might get certificate errors in Ruby 2.0 when talking HTTPS is because there isn't a default certificate bundle that OpenSSL (which was used when building Ruby) trusts.

Update: this problem is solved in edge versions of rbenv and RVM.

$ ruby -rnet/https -e "Net::HTTP.get URI('https://github.com')"
net/http.rb:917:in `connect': SSL_connect returned=1 errno=0 state=SSLv3
  read server certificate B: certificate verify failed (OpenSSL::SSL::SSLError)

You can work around the issue by installing a certificate bundle that you trust. I trust Mozilla and curl.

piscisaureus

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = [email protected]:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:

ls-lukebowerman

<% pages = sitemap.resources.find_all{|p| p.source_file.match(/\.html/) } %>
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<% pages.each do |p| %>
  <url>
    <loc>http://youdomain.com/<%=p.destination_path.gsub('/index.html','')%></loc>
    <priority>0.7</priority>
  </url>
<% end %>
</urlset>

frank-who

#!/usr/bin/env bash

# Usage: curl -L https://raw.github.com/gist/3277326/ubuntu_bootstrap.sh | bash

RUBY=1.9.3-p327

echo "Updating Packages"; echo
apt-get -y update && apt-get -y upgrade
apt-get -y install build-essential zlib1g-dev libssl-dev libreadline6-dev libyaml-dev libgdbm-dev libxml2 libxml2-dev libxslt-dev git-core

toolmantim

Retaining line numbers with the Rails asset pipeline

By default the Rails 3 asset pipeline uses the Uglifier gem to optimize and minify your Javascript. One of its many optimisations is to remove all whitespace, turning your Javascript into one very long line of code.

Whist removing all the newlines helps to reduce the file size, it has the disadvantage of making your Javascript harder to debug. If you've tried to track down Javascript errors in minified Javascript files you'll know the lack of whitespace does make life harder.

Luckily there is a simple solution: to configure Uglifier to add newlines back into the code after it performs its optimisations. And if you're serving your files correctly gzip'd, the newlines add only a small increase to the final file size.

You can configure Uglifier to add the newlines by setting the following in your Rails 3 config/production.rb file: