chrisroos

Every so often I have to restore my gpg keys and I'm never sure how best to do it. So, I've spent some time playing around with the various ways to export/import (backup/restore) keys.

Method 1

Backup the public and secret keyrings and trust database

cp ~/.gnupg/pubring.gpg /path/to/backups/
cp ~/.gnupg/secring.gpg /path/to/backups/
cp ~/.gnupg/trustdb.gpg /path/to/backups/

or, instead of backing up trustdb...

peterhellberg

guard 'shell' do
  watch(/relation_tree_spec\.rb/) { `clear && ruby relation_tree_spec.rb` }
end

hxgdzyuyi

define('backbone', ['lib-underscore', 'lib-backbone'], function () {
  Backbone.mixin = function (view, mixin, custom) {
    if (custom) {
      if (custom.events && mixin.events) {
        mixin = _.clone(mixin)
        _.defaults(custom.events, mixin.events)
      }
      _.extend(mixin, custom)
    }
    var source = view.prototype || view

fnielsen

# python2.6

'Finn Årup Nielsen'

u'Finn Årup Nielsen'

unicode('Finn Årup Nielsen', 'utf-8')


# So what is wrong with that?}

nateware

#
# Sample nginx.conf optimized for EC2 c1.medium to xlarge instances.
# Also look at the haproxy.conf file for how the backend is balanced.
#

user "nginx" "nginx";
worker_processes 10;

error_log  /var/log/nginx_error.log info;

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/

inklesspen

Pytest's session fixture scope is really handy, but there are some things which need to execute only once per actual test session. For example, one of my session fixtures sets up DB tables at the start of the test session and tears them down at the end. (I use PostgreSQL's nested transactions to keep from having to drop and recreate tables between each individual test.)

@pytest.fixture(scope='session')
def dbtables(request, sqlengine):
    Base.metadata.create_all(sqlengine)

    def teardown():
        Base.metadata.drop_all(sqlengine)

alopes

de 
a 
o 
que 
e 
do 
da 
em 
um 
para 

jasonbartz

Deploying pypy on uwsgi

Instructions are kind of sporadic around the internet, so I thought I would gather them all in one place. The following example uses a Flask app as the thing deployed. You should only have to this once, and then you can pass the bin around.

Requirements

• pypy 2.x (tested)
• uwsgi 1.9.11+ (trunk as of this gist)

Build translated pypy binary and pypy lib.

philipcristiano

import sys

from PIL import Image, ImageDraw

try:
    import cv
except ImportError:
    print 'Could not import cv, trying opencv'
    import opencv.cv as cv