tollmanz

# Install dependencies
# 
# * checkinstall: package the .deb
# * libpcre3, libpcre3-dev: required for HTTP rewrite module
# * zlib1g zlib1g-dbg zlib1g-dev: required for HTTP gzip module
apt-get install checkinstall libpcre3 libpcre3-dev zlib1g zlib1g-dbg zlib1g-dev && \

mkdir -p ~/sources/ && \

# Compile against OpenSSL to enable NPN

chanks

Turning PostgreSQL into a queue serving 10,000 jobs per second

RDBMS-based job queues have been criticized recently for being unable to handle heavy loads. And they deserve it, to some extent, because the queries used to safely lock a job have been pretty hairy. SELECT FOR UPDATE followed by an UPDATE works fine at first, but then you add more workers, and each is trying to SELECT FOR UPDATE the same row (and maybe throwing NOWAIT in there, then catching the errors and retrying), and things slow down.

On top of that, they have to actually update the row to mark it as locked, so the rest of your workers are sitting there waiting while one of them propagates its lock to disk (and the disks of however many servers you're replicating to). QueueClassic got some mileage out of the novel idea of randomly picking a row near the front of the queue to lock, but I can't still seem to get more than an an extra few hundred jobs per second out of it under heavy load.

So, many developers have started going straight t

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

renechz

/* Keybindings for SublimeGit with Vintage mode enabled on OSX.
 * 
 * Using Vim Fugitive keybindings when possible.
 * Using "," as leader key.
 *
 * Work in progress. 
 * Definitely not a much advanced user of either Vim or Fugitive, but it's a start.
 */
[
    /*** GIT STATUS ***/

brolewis

'''Zookeeper-based Scheduler'''
## Standard Library
import cPickle           # Store dictionary in ZooKeeper
import datetime          # Time delta
import socket            # Hostname
## Third Party
import celery            # Current app
import celery.beat       # Scheduler
import celery.utils.log  # Get logger
import kazoo.client      # ZooKeeper Client Library

willurd

Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000. Use this power wisely.

Discussion on reddit.

Python 2.x

$ python -m SimpleHTTPServer 8000

ju-popov

######################################################################
#  CURRENT AWARE LOCAL DATETIME
######################################################################

from datetime import datetime
from tzlocal import get_localzone

local_tz = get_localzone()
local_dt = datetime.now(local_tz)

johnkary

Fixing NFS disconnecting with Vagrant and VirtualBox on Mac OS

Symptoms and Known Conditions

• Mac OS host machine (10.6+)
• VirtualBox (4.1+)
• Vagrant (1.0+)
• Connecting via VPN to a remote network
• Mounting a directory from your host machine to the guest machine using NFS with something like this:

inklesspen

(This gist is pretty old; I've written up my current approach to the Pyramid integration on this blog post, but that blog post doesn't go into the transactional management, so you may still find this useful.)

Fast and flexible unit tests with live Postgres databases and fixtures

I've created a Pyramid scaffold which integrates Alembic, a migration tool, with the standard SQLAlchemy scaffold. (It also configures the Mako template system, because I prefer Mako.)

I am also using PostgreSQL for my database. PostgreSQL supports nested transactions. This means I can setup the tables at the beginning of the test session, then start a transaction before each test happens and roll it back after the test; in turn, this means my tests operate in the same environment I expect to use in production, but they are also fast.

I based my approach on [sontek's blog post](http://sontek.net/blog/

dhendo

import mongoengine
class MongoModelSerializer(serializers.ModelSerializer):

    def get_default_fields(self):
        cls = self.opts.model
        opts = get_concrete_model(cls)
        #pk_field = opts.pk
        fields = []
        fields += [getattr(opts, field) for field in opts._fields]
        #fields += [field for field in opts.many_to_many if field.serialize]