mohakevin

Create the appropriate VPC that your application is going to live in. Create subnets for each availability zone you want to use.
Create VPC security group(s) for your auto-scaling instances. For example, if you're going to auto-scale web servers, create a "web" VPC security group.
Go into AWS console and create an ELB. Easy wizard. Select HTTP and (if needed) HTTPS. Make sure it's associated with the VPC you created in step 1.
Create an auto-scaling launch configuration from the CLI. The launch configuration has the AMI, size, and security group from step #2. The security group must be by ID not name ("sg-12345"):
```
   as-create-launch-config web --image-id ami-2e31bf1e --instance-type m1.medium \
```

-g sg-7619041a --key root

Installing Graphite:

Graphite does two things:

Store numeric time-series data
Render graphs of this data on demand

What Graphite does not do is collect data for you, however there are some tools out there that know

The prep-script.sh will setup the latest Node and install the latest perf version on your Linux box.

When you want to generate the flame graph, run the following (folder locations taken from install script):

sudo sysctl kernel.kptr_restrict=0
# May also have to do the following:
# (additional reading http://unix.stackexchange.com/questions/14227/do-i-need-root-admin-permissions-to-run-userspace-perf-tool-perf-events-ar )
sudo sysctl kernel.perf_event_paranoid=0

Nginx FastCGI response buffer sizes

By default when Nginx starts receiving a response from a FastCGI backend (such as PHP-FPM) it will buffer the response in memory before delivering it to the client. Any response larger than the set buffer size is saved to a temporary file on disk.

This process is outlined at the Nginx ngx_http_fastcgi_module page manual page.

Introduction
Determine actual FastCGI response sizes
Setting the buffer size
Verifying results

	# This is a template .gitignore file for git-managed WordPress projects.
	#
	# Fact: you don't want WordPress core files, or your server-specific
	# configuration files etc., in your project's repository. You just don't.
	#
	# Solution: stick this file up your repository root (which it assumes is
	# also the WordPress root directory) and add exceptions for any plugins,
	# themes, and other directories that should be under version control.
	#
	# See the comments below for more info on how to add exceptions for your

	# References:
	# http://blog.mixu.net/2011/08/13/nginx-websockets-ssl-and-socket-io-deployment/
	# http://blog.exceliance.fr/2012/09/10/how-to-get-ssl-with-haproxy-getting-rid-of-stunnel-stud-nginx-or-pound/
	#

	global
	nbproc 2
	maxconn 16384

	defaults

	##
	## This nginx.conf servers as the main config file for webflow reverse proxy
	##
	## RCS:
	## https://gist.github.com/sansmischevia/5617402
	##
	## Hardening tips:
	## http://www.cyberciti.biz/tips/linux-unix-bsd-nginx-webserver-security.html
	##

	#####################################################
	#
	# Provided by the Magento Support Center
	# http://magentosupport.help/knowledgebase/configuring-nginx-to-work-with-magento-advanced/
	#
	# Your Magento Tutorial specialists
	#
	server {
	listen *:8080;
	server_name fanatik.redrokk.com www.fanatikbike.com fanatikbike.com;

	#!/bin/bash
	#
	# transcode-video.sh
	#
	# Copyright (c) 2013-2015 Don Melton
	#

	about() {
	cat <<EOF
	$program 5.13 of April 8, 2015

	[oracle@database scripts]$ crontab -l
	# Perform full backup on database Sunday at 3:05 am
	5 3 * * 0 /$HOME/scripts/backup_db database_name full > /$HOME/scripts/logs/full_backup.log
	# Perform incremental backups on database Mon-Sat at 3:05 am
	5 3 * * 1-6 /$HOME/scripts/backup_db database_name inc > /$HOME/scripts/logs/inc_backup.log