schmengler

<?php
/**
 * Integration test for OnePageCheckout
 *
 * @author Fabian Schmengler <fschmengler@sgh-it.eu>
 * @copyright SGH informationstechnologie UGmbH 2012
 * @package SGH\Common
 * @subpackage Test
 *
 */

nvk

### Instructions source http://tumblr.intranation.com/post/766290743/using-dropbox-git-repository ####

-- make empty repo on dropbox:
	cd ~/Dropbox/RipeApps/Git
	mkdir -p newname.git
	cd !$
	git --bare init

-- push your junk into it
	cd ~/Projects/myrepo

bcomnes

; Global settings
[redshift]
temp-day=6500K
temp-night=5000
transition=1
;gamma=0.8:0.7:0.8
gamma=1.000:1.000:1.000
location-provider=geoclue
;location-provider=manual
adjustment-method=vidmode

leek

Writing Magento Modules

All custom modules should have a Namespace and Module Name. These are used below as {Namespace} and {Module}.

Caution: The Magento autoloader is known to have problems with CamelCase namespaces and/or modules between Windows and *nix systems. If your module requires more than one word for either of these, it is best to just concatenate them to avoid any issues (Example: {Namespace}_{Examplemodule}).

Index

• Directory Structure

acdha

        client = paramiko.SSHClient()
        client._policy = paramiko.WarningPolicy()
        client.set_missing_host_key_policy(paramiko.AutoAddPolicy())

        ssh_config = paramiko.SSHConfig()
        user_config_file = os.path.expanduser("~/.ssh/config")
        if os.path.exists(user_config_file):
            with open(user_config_file) as f:
                ssh_config.parse(f)

be9

def paginate(scope, default_per_page = 20)
  collection = scope.page(params[:page]).per((params[:per_page] || default_per_page).to_i)

  current, total, per_page = collection.current_page, collection.num_pages, collection.limit_value

  return [{
    pagination: {
      current:  current,
      previous: (current > 1 ? (current - 1) : nil),
      next:     (current == total ? nil : (current + 1)),

JeffreyWay

set nocompatible   " Disable vi-compatibility
set t_Co=256

colorscheme xoria256
set guifont=menlo\ for\ powerline:h16
set guioptions-=T " Removes top toolbar
set guioptions-=r " Removes right hand scroll bar
set go-=L " Removes left hand scroll bar
set linespace=15

EvanK

<phpunit>
    <testsuites>
        <testsuite name="Unit">
            <directory>../src/*/Bundle/*Bundle/Tests</directory>
            <exclude>src/*/Bundle/*Bundle/Tests/Functional</exclude>
        </testsuite>
</phpunit>

sumeetpareek

#!/usr/bin/env python2
"""A very simple Apache access log parser in Python

usage help = http://i.imgur.com/XBiX2kX.png

when required arguments are missing = http://i.imgur.com/P5L0GZV.png

when incorrect file path is passed = http://i.imgur.com/sJDc0om.png

successful sample output = http://i.imgur.com/iH89mwI.png

Chaser324

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j