jbenet

a simple git branching model (written in 2013)

This is a very simple git workflow. It (and variants) is in use by many people. I settled on it after using it very effectively at Athena. GitHub does something similar; Zach Holman mentioned it in this talk.

Update: Woah, thanks for all the attention. Didn't expect this simple rant to get popular.

blockjon

+----------------+-------+---------------------+---------------------+
| sender_user_id | name  | num_users_contacted | num_users_responded |
+----------------+-------+---------------------+---------------------+
|              3 | Greg  |                   1 |                   1 |
|              1 | John  |                   4 |                   0 |
|              7 | Linda |                   1 |                   1 |
|              6 | Sue   |                   2 |                   2 |
+----------------+-------+---------------------+---------------------+

blockjon

+----+-------+-------------------------------+
| id | name  | total_cold_inquiries_received |
+----+-------+-------------------------------+
|  2 | Mike  |                             1 |
|  4 | Bill  |                             2 |
|  5 | Kate  |                             1 |
|  6 | Sue   |                             1 |
|  7 | Linda |                             2 |
|  8 | Mary  |                             1 |
+----+-------+-------------------------------+

funkotron

#!/bin/bash
# Description: Using Docker (requires docker to be installed http://www.docker.io/gettingstarted/ ), spawn a postgresql instance and a dynamically configured treeio instance
# Also requires postgresql client tools http://www.postgresql.org/download/linux/ubuntu/
# Run chmod +x to make this file executable then run it: ./docker_create_treeio.sh
# Author: Adam Awan
# Email: adam@tree.io

# Set the port to forward for Tree.io
TREEIO_PORT="80"

olivierlacan

Screencasting Framework

The following document is a written account of the Code School screencasting framework. It should be used as a reference of the accompanying screencast on the topic.

Why you should care about screencasting?

You're probably aren't going to take the time to read this document if you're not interested, but there are a lot of nice side effects caused by learning how to create quality screencasts.

1. Communicating more effectively - At Envy Labs we produce screencasts for our clients all the time. Whether it's demoing a new feature or for a presentation for an invester, they're often much more effective and pleasent than a phone call or screen sharing.

marktheunissen

This playbook has been removed as it is now very outdated.

eclubb

#!/bin/sh

# This script will migrate schema and data from a SQLite3 database to PostgreSQL.
# Schema translation based on http://stackoverflow.com/a/4581921/1303625.
# Some column types are not handled (e.g blobs).

SQLITE_DB_PATH=$1
PG_DB_NAME=$2
PG_USER_NAME=$3

jimklo

I'm new to PyF... it looks like great framework to build workflow applications.

I'm running into an issue which I'm not quite sure how to solve before I give up on PyF...

Following the install guide, I've setup a virtualenv, and activated it... then:

     easy_install -UZ pyf[fullstack]

After some time easy_install seems to fail:

leshill

web: bundle exec unicorn -p $PORT -c ./config/unicorn.rb

drewda

# note that this function is called whenever a GeoPoint model changes
# Backbone will pass in geo_point, which refers to the changed model
# @geo_points refers to the entire collection of GeoPoint models

# update the bound data
geo_points = @geo_points.reject (gp) => gp.get('markedForDelete')

geoPointMarkers = d3.select('#geo-point-layer').selectAll("g")
                    .data geo_points, (d) =>
                      d.cid