favadi

[program:redmine]
command=/home/redmine/start_redmine.sh
user=redmine
directory=/home/redmine
stderr_logfile=/var/log/supervisor/redmine_error.log
stdout_logfile=/var/log/supervisor/redmine_out.log
environment=HOME="/home/redmine"

prio

defmodule Tcprpc.Server do
  use GenServer.Behaviour

  defrecord State, port: nil, lsock: nil, request_count: 0

  def start_link(port) do
    :gen_server.start_link({ :local, :tcprcp }, __MODULE__, port, [])
  end

  def start_link() do

juanqui

// helpful links:
// https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man2/EV_SET.2.html
// http://julipedia.meroh.net/2004/10/example-of-kqueue.html

// create kqueue
kq, err := syscall.Kqueue()
if err != nil {
	log.Println("Error creating Kqueue descriptor!")
	return
}

joyrexus

Sans jQuery

Events

// jQuery
$(document).ready(function() {
  // code
})

mgedmin

How to get a free StartSSL.com SSL certificate

I'm writing this up from memory, so errors may appear.

This has been updated to use SHA256 certificates.

Start

1. Go to http://www.startssl.com/
2. Click on 'Control Panel'

mikeverbeck

include_recipe "ohai"

bin_path = ::File.join(node['rbenv']['root_path'], "bin", "rbenv")

template "#{node[:ohai][:plugin_path]}/rbenv.rb" do
  source 'plugins/rbenv.rb.erb'
  owner 'root'
  group 'root'
  mode 0755

koenpunt

select.form-control + .chosen-container.chosen-container-single .chosen-single {
    display: block;
    width: 100%;
    height: 34px;
    padding: 6px 12px;
    font-size: 14px;
    line-height: 1.428571429;
    color: #555;
    vertical-align: middle;
    background-color: #fff;

ilyakatz

In order to use asset pipeline available for static error pages (like 404.html), a few steps are required

• Move static pages from /public into /app/assets

  (eg: public/422.html → app/assets/html/422.html.erb)

• Add html directory to the asset pipeline

• Update exceptions middleware to understand assets with digests

jed

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

• Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.

• Use production SSL certificates locally. This is annoying

gitaarik

0-mail.com
0815.ru
0845.ru
0clickemail.com
0wnd.net
0wnd.org
10minutemail.com
10minutemail.net
12houremail.com
12minutemail.com