groner

'''Hooks for lettuce to run a test pylons server'''

import threading
from os import getcwd

import pylons.test

from paste.deploy.loadwsgi import loadapp
from paste.httpserver import serve
from paste.script.appinstall import SetupCommand

lettertwo

path = require 'path'
webpack = require 'webpack'
fs = require 'fs'
ExtractTextPlugin = require 'extract-text-webpack-plugin'
ProgressPlugin = require 'webpack/lib/ProgressPlugin'
flag = require 'node-env-flag'
settings = require './src/settings'


scriptExportsLoader = path.join __dirname, 'script-exports-loader'

tupy

# -*- mode: ruby -*-
# vi: set ft=ruby : 
# David Lutz's Multi VM Vagrantfile
# inspired from Mark Barger's https://gist.github.com/2404910

boxes = [
  { :name => :web,    :role => 'web_dev',     :ip => '192.168.33.1', :ssh_port => 2201, :http_fwd => 9980, :cpus =>4, :shares => true },
  { :name => :data,        :role => 'data_dev',         :ip => '192.168.33.2', :ssh_port => 2202, :mysql_fwd => 9936, :cpus =>4 },
  { :name => :railsapp,    :role => 'railsapp_dev',     :ip => '192.168.33.3', :ssh_port => 2203, :http_fwd => 9990, :cpus =>1}
]

gnap

var crypto = require('crypto');

function create_signature(secret, name, parts) {
    var hmac = crypto.createHmac('sha1', secret);
    hmac.update(name);
    for (var i = 0; i < parts.length; i++) {
        hmac.update(parts[i]);
    }
    return hmac.digest('hex');
}

dergachev

Trying Vagrant / LXC / Docker

LXC

Here are some LXC links:

• https://github.com/portertech/kitchen-lxc
• https://github.com/chrisroberts/vagabond/blob/master/USAGE.md (lxc based alternative to Vagrant)
• https://github.com/fgrehm/vagrant-lxc and http://fabiorehm.com/blog/2013/04/28/lxc-provider-for-vagrant/
• http://webcache.googleusercontent.com/search?q=cache:http://stgraber.org/2012/05/04/lxc-in-ubuntu-12-04-lts/

MLnick

import sys

from pyspark.context import SparkContext
from numpy import array, random as np_random
from sklearn import linear_model as lm
from sklearn.base import copy

N = 10000   # Number of data points
D = 10      # Numer of dimensions
ITERATIONS = 5

lepture

def runserver(port=5000, profile_log=None):
    """Runs a development server."""
    from gevent.wsgi import WSGIServer
    from werkzeug.serving import run_with_reloader
    from werkzeug.debug import DebuggedApplication
    from werkzeug.contrib.profiler import ProfilerMiddleware

    port = int(port)

    if profile_log:

michaelneale

#!/bin/sh                                                                                                                                                                            

remove_dangling() {
   echo "Removing dangling images ..."
   docker rmi $(docker images -f dangling=true -q)
}

remove_stopped_containers() {
    echo "Removing stopped containers ..."
    docker rm $(docker ps -qa)

danawoodman

WebSockets + Reflux + React

Using WebSockets, React and Reflux together can be a beautiful thing, but the intial setup can be a bit of a pain. The below examples attempt to offer one (arguably enjoyable) way to use these tools together.

Overview

This trifect works well if you think of things like so:

1. Reflux Store: The store fetches, updates and persists data. A store can be a list of items or a single item. Most of the times you reach for this.state in react should instead live within stores. Stores can listen to other stores as well as to events being fired.
2. Reflux Actions: Actions are triggered by components when the component wants to change the state of the store. A store listens to actions and can listen to more than one set of actions.

flores

global 
  log 127.0.0.1 local0 notice 
  maxconn 50000
  daemon 
  stats socket /tmp/proxystats level admin
defaults
  log global 
  mode http 
  option httplog 
  option dontlognull