Marcus Sá marcusvmsa

## GIF-Screencast-OSX.md

      
              2 files
            
          
              0 forks
            
          
              0 comments
            
          
              1 star
            
          
                marcusvmsa
                / GIF-Screencast-OSX.md
            
            
              Created
              July 24, 2013 01:42
                — forked from dergachev/GIF-Screencast-OSX.md
            
          
    OS X Screencast to animated GIF

This gist shows how to create a GIF screencast using only free OS X tools: QuickTime, ffmpeg, and gifsicle.

Instructions

To capture the video (filesize: 19MB), using the free "QuickTime Player" application:

  
## gist:5515208

How to setup Heroku Hostname SSL with GoDaddy SSL Certificate and Zerigo DNS
Heroku recently added an exciting new 'Hostname SSL' option.  This option offers the broad compatibility of IP-based SSL, but at 1/5 the price ($20 / month at the time of this writing).

The following tutorial explains how to use Heroku's new 'Hostname SSL' option on your Heroku project.  Before we begin, let's list what we're using here:

    * Heroku Hostname SSL
    * GoDaddy Standard SSL Certificate
    * Zerigo DNS

## attr_acessible_security.rb
# Put this file on config/initializer

# This will create an empty whitelist of attributes available for mass assignment for
# all models in your app. As such, your models will need to explicitly whitelist
# accessible parameters by using an attr_accessible declaration. This technique is best
# applied at the start of a new project. However, for an existing project with a thorough
# set of functional tests, it should be straightforward and relatively quick to insert this
# initializer, run your tests, and expose each attribute (via attr_accessible) as dictated
# by your failing tests.

## spawn-fcgi.sh
spawn-fcgi -a 127.0.0.1 -p 53217 -P /var/run/fastcgi-php.pid -- /usr/bin/php-cgi

## .bashrc
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples

# If not running interactively, don't do anything
[ -z "$PS1" ] && return

# don't put duplicate lines in the history. See bash(1) for more options
export HISTCONTROL=ignoredups
# ... and ignore same sucessive entries.

	How to setup Heroku Hostname SSL with GoDaddy SSL Certificate and Zerigo DNS
	Heroku recently added an exciting new 'Hostname SSL' option. This option offers the broad compatibility of IP-based SSL, but at 1/5 the price ($20 / month at the time of this writing).

	The following tutorial explains how to use Heroku's new 'Hostname SSL' option on your Heroku project. Before we begin, let's list what we're using here:

	* Heroku Hostname SSL
	* GoDaddy Standard SSL Certificate
	* Zerigo DNS
	# Put this file on config/initializer

	# This will create an empty whitelist of attributes available for mass assignment for
	# all models in your app. As such, your models will need to explicitly whitelist
	# accessible parameters by using an attr_accessible declaration. This technique is best
	# applied at the start of a new project. However, for an existing project with a thorough
	# set of functional tests, it should be straightforward and relatively quick to insert this
	# initializer, run your tests, and expose each attribute (via attr_accessible) as dictated
	# by your failing tests.
	# ~/.bashrc: executed by bash(1) for non-login shells.
	# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
	# for examples

	# If not running interactively, don't do anything
	[ -z "$PS1" ] && return

	# don't put duplicate lines in the history. See bash(1) for more options
	export HISTCONTROL=ignoredups
	# ... and ignore same sucessive entries.