skorfmann

require 'dnsimple'
require 'platform-api'

namespace :staging do
  desc "create subdomain DNS record for Heroku review app"
  task :publish_dns do
    heroku_app_name = ENV['HEROKU_APP_NAME']
    heroku_app_name =~ /.*(pr-\d+)/

    subdomain          = $1

monochromegane

速習Go

Go環境のつくりかた

MacOSX

homebrewでインストール

$ brew update

how_to_use_swift_in_terminal.md

How to use swift in your terminal

setup

First, install Xcode 6 beta.

And run it.

sudo xcode-select -switch /Applications/Xcode6-Beta.app/Contents/Developer

knibals

package main

import (
  "encoding/json"
	"errors"
	"flag"
	"fmt"
	"io/ioutil"
	"log"
	"net"

hgfischer

Benchmarking Nginx with Go

There are a lot of ways to serve a Go HTTP application. The best choices depend on each use case. Currently nginx looks to be the standard web server for every new project even though there are other great web servers as well. However, how much is the overhead of serving a Go application behind an nginx server? Do we need some nginx features (vhosts, load balancing, cache, etc) or can you serve directly from Go? If you need nginx, what is the fastest connection mechanism? This are the kind of questions I'm intended to answer here. The purpose of this benchmark is not to tell that Go is faster or slower than nginx. That would be stupid.

So, these are the different settings we are going to compare:

• Go HTTP standalone (as the control group)
• Nginx proxy to Go HTTP
• Nginx fastcgi to Go TCP FastCGI
• Nginx fastcgi to Go Unix Socket FastCGI

amatsuda

Kernel.class_eval do
  #FIXME this is terrible
  def static(meth)
    define_singleton_method(meth) do |*args, &b|
      new.send meth, *args, &b
    end
    meth
  end

  def abstract(meth)

textarcana

XWindows for Headless Selenium

How to set up a Headless Selenium Testing environment for CentOS 6.3.

On your CentOS 6.3 host

Follow these steps to set up a CentOS 6.3 host to run headless Selenium tests with Firefox.

hsbt

2013 年の新卒研修メニュー

Rails Tutorial

目的

• 2013 年で Web アプリケーションを作る時にモダンな方法で一通り Web アプリケーションを自分一人で作れるようになってもらう
• 作る過程で Web 開発で必要とされるスキルセットを身につけてもらう

教材と教える項目

taea

git-cherry-pick で master のSassを最新に

トピックブランチでデザイン作業後、masterにマージされるまでの間、masterのSassが最新のものから乖離してしまって作業が進められない問題を解決するために、git-cherry-pickで必要なSassの変更のみをmasterに取り込む

※この際、Sassだけcommitを分けると楽 → 不要なファイルやコンフリクトがなければそのままcommitごとmasterに取り込まれるので超ベンリです。

手順

作業中のトピックブランチで git log して必要なcommitのIDをコピー

$ git log

commit一覧が出てくるので、masterに取り込みたい「commit」の右側の文字列をコピー（下記の場合は 88ca4f2b3958748baf9947dcf1fdaebc01616cf6 をコピー）

mreinsch

load 'deploy' unless defined?(_cset)

_cset :asset_env, "RAILS_GROUPS=assets"
_cset :assets_prefix, "assets"
_cset :assets_role, [:web]

_cset :normalize_asset_timestamps, false

after 'deploy:update_code', 'deploy:assets:precompile'