Peng Du gnepud

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.

Since this is on Hacker News and reddit...

No, I don't distribute my résumé like this. A friend of mine made a joke about me being the kind of person who would do this, so I did (the link on that page was added later). My actual résumé is a good bit crazier.
I apologize for the use of _t in my types. I spend a lot of time at a level where I can do that; "reserved for system libraries? I am the system libraries".
Since people kept complaining, I've fixed the assignments of string literals to non-const char *s.
My use of type * name, however, is entirely intentional.
If you're using an older compiler, you might have trouble with the anonymous unions and the designated initializers - I think gcc 4.4 requires some extra braces to get them working together. Anything reasonably recent should work fine. Clang and gcc (newer than 4.4, at le

Sinatra like routes in Rails controllers

A proof of concept of having Sinatra like routes inside your controllers.

How to use

Since the router is gone, feel free to remove config/routes.rb. Then add the file below to lib/action_controller/inline_routes.rb inside your app.

unicorn config file

Edit file /home/gitlab/gitlab/config/unicorn.rb

Find line listen "#{app_dir}/tmp/sockets/gitlab.socket" and comment it. Uncomment line listen "127.0.0.1:8080"

required modules for apache

sudo a2enmod proxy
sudo a2enmod proxy_balancer

I'm a fan of MiniTest::Spec. It strikes a nice balance between the simplicity of TestUnit and the readable syntax of RSpec. When I first switched from RSpec to MiniTest::Spec, one thing I was worried I would miss was the ability to add matchers. (A note in terminology: "matchers" in MiniTest::Spec refer to something completely different than "matchers" in RSpec. I won't get into it, but from now on, let's use the proper term: "expectations").

Understanding MiniTest::Expectations

Let's take a look in the code (I'm specifically referring to the gem, not the standard library that's built into Ruby 1.9):

# minitest/spec.rb

module MiniTest::Expectations

	class TracePoint
	class Middleware

	def initialize(app)
	@app = app
	end

	def call(env)
	stats = {}
	trace = TracePoint.new(:call) do \|tp\|

	// Source: https://groups.google.com/forum/#!topic/angular/hVrkvaHGOfc
	// jsFiddle: http://jsfiddle.net/pkozlowski_opensource/PxdSP/14/
	// author: Pawel Kozlowski

	var myApp = angular.module('myApp', []);

	//service style, probably the simplest one
	myApp.service('helloWorldFromService', function() {
	this.sayHello = function() {
	return "Hello, World!"

	/**********************************************/
	/*
	/* IR_Black Skin by Ben Truyman - 2011
	/*
	/* Based on Todd Werth's IR_Black:
	/* http://blog.toddwerth.com/entries/2
	/*
	/* Inspired by Darcy Clarke's blog post:
	/* http://darcyclarke.me/design/skin-your-chrome-inspector/
	/*

	require 'minitest/autorun'

	module MiniTest::Assertions
	def assert_changes(obj, method, exp_diff)
	before = obj.send method
	yield
	after = obj.send method
	diff = after - before

	assert_equal exp_diff, diff, "Expected #{obj.class.name}##{method} to change by #{exp_diff}, changed by #{diff}"

	<!DOCTYPE html>
	<html>
	<head>
	<title>Determine Link Trigger Method With jQuery</title>
	</head>
	<body>

	<h1>
	Determine Link Trigger Method With jQuery
	</h1>