0xjac

The repository for the assignment is public and Github does not allow the creation of private forks for public repositories.

The correct way of creating a private frok by duplicating the repo is documented here.

For this assignment the commands are:

1. Create a bare clone of the repository. (This is temporary and will be removed so just do it wherever.)

git clone --bare git@github.com:usi-systems/easytrace.git

tomysmile

type below:

brew update
brew install redis

To have launchd start redis now and restart at login:

brew services start redis

steshaw

#!/bin/bash

#
# Adapted from http://blog.strug.de/2012/06/my-homebrew-multi-user-setup/
#

sudo dseditgroup -q -o create brew
sudo dseditgroup -o edit -a ${USER} -t user brew
sudo chgrp -R brew /usr/local # Change the group of homebrew installation directory.
sudo chmod -R g+w /usr/local # Allow group members to write inside this directory.

calmyournerves

# make sure the following is installed:
# - Xcode Command Line Tools (xcode-select --install)
# - OpenSSL from homebrew (brew install openssl && brew link openssl --force)

# dependencies and preparations
brew update
brew install git ossp-uuid md5sha1sum coreutils pcre gnutls libidn gsasl pkg-config libxml2
brew link libxml2 --force
brew tap darinmorrison/haskell
brew install darinmorrison/haskell/cabal-install

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

olasitarska

# -*- coding: utf-8 -*-
"""
Builds epub book out of Paul Graham's essays: http://paulgraham.com/articles.html

Author: Ola Sitarska <ola@sitarska.com>
Copyright: Licensed under the GPL-3 (http://www.gnu.org/licenses/gpl-3.0.html)

This script requires python-epub-library: http://code.google.com/p/python-epub-builder/
"""

chriscoyier

Yaron Schoen
http://yaronschoen.com/
http://www.yaronschoen.com/site/atom/

Oli Studholme
http://oli.jp/
http://oli.jp/articles.atom

Ben Bleikamp
http://www.bleikamp.com