ggl

#!/usr/bin/env perl
#
#  htpasswd.pl
#  
# Copyright (c) 2013, Gelu Lupas <[email protected]>
#
# Permission to use, copy, modify, and/or distribute this software for any
# purpose with or without fee is hereby granted, provided that the above
# copyright notice and this permission notice appear in all copies.
#

westonruter

<?php
/*
Usage:
	cache_fragment_output( 'unique-key', 3600, function () {
		functions_that_do_stuff_live();
		these_should_echo();
	});
*/

function cache_fragment_output( $key, $ttl, $function ) {

ryanburnette

Moved ... https://github.com/ryanburnette/fragment-cache

clarkdave

line = '127.0.0.1 gateway.internal gateway'

file = Chef::Util::FileEdit.new('/etc/hosts')
file.insert_line_if_no_match(/#{line}/, line)
file.write_file

cheeaun

JavaScript error logging services

To allow easier contributions, I've moved this to https://github.com/cheeaun/javascript-error-logging. Thanks! 😄

• http://errorception.com/ - translate error messages to English
• http://www.exceptionhub.com/
• http://jserrlog.appspot.com/
• http://www.muscula.com/ - source maps, translate error messages to English
• https://www.airbrake.io/ - tracekit, source maps

alvarobp

Disclaimer: The following examples try to give an overview of the process followed in different scenarios. Some commands were actually written from memory. Some tools might exist simplifying all this. Furthermore, I'm no expert so if anyone ever reads this and knows any improvement, please let me know.

Case 1: Direct access to Pairing Station

Given that the Guest User can access the Pairing Station directly, either because the station is publicly available or because NAT port forwarding can be used, there's only one thing we need to do, give ssh access to the Guest User by adding his ssh public key to our Local User (pair) .ssh/authorized_keys file.

The local user would open up a tmux session with

tmux new-session -s pairing

christianberg

#!/bin/bash
set -e

SECRETFILE=~/.digitalocean
if [[ -z $DIGOCEAN_ID ]] || [[ -z $DIGOCEAN_KEY ]]; then
    if [ -e $SECRETFILE ]; then
        . $SECRETFILE
    fi
fi

drawveloper

How to: Allow Node to bind to port 80 without sudo

TL;DR

Only do this if you understand the consequences: all node programs will be able to bind on ports < 1024

sudo setcap 'cap_net_bind_service=+ep' /usr/local/bin/node

Important: your node location may vary. Use which node to find it, or use it directly in the command:

trey

module.exports = function(grunt) {

  // Project configuration.
  grunt.initConfig({
    pkg: grunt.file.readJSON('package.json'),
    connect: {
      server: {
        options: {},
      }
    },

branneman

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions