SpivEgin

# Installer Script to take a stock Centos 6.5 to a FreePBX Distro 5.211.65 release.
# Once completed you can use the upgrade scripts for version track 5.211.65
# To keep your system updated.

# Copyright 2013 Schmooze Com, Inc.

# This script is not to be copied for other use.

# This script and the finished product that is installed carries NO WARRANTY and is
# used to get your FreePBX system setup and installed.  The installed product is released

SpivEgin

curl -s https://api.github.com/orgs/[Insert Organization]/repos?per_page=500 | ruby -rubygems -e 'require "json"; JSON.load(STDIN.read).each { |repo| %x[git clone #{repo["ssh_url"]} ]}'

SpivEgin

curl -s https://api.github.com/orgs/PrestaShop/repos | ruby -rjson -e 'JSON.load(STDIN.read).each {|repo| %x[git clone #{repo["ssh_url"]} --recursive]}'

SpivEgin

#!/bin/bash
# Inspired by http://verbally.flimzy.com/install-couchdb-1-6-1-debian-8-2-jessie/

# Erlang
echo -e "deb http://packages.erlang-solutions.com/debian jessie contrib" | sudo tee /etc/apt/sources.list.d/erlang-solutions.list
wget -qO - http://packages.erlang-solutions.com/debian/erlang_solutions.asc | sudo apt-key add -

# Update packages
sudo apt-get update

SpivEgin

#!/bin/sh

DEBMLOG=/pool/debmirror/debmirror.log
MIRRORDIR=/pool/debmirror
BANDWIDTH=500

if test -s $DEBMLOG
then
test -f $DEBMLOG.3.gz && mv $DEBMLOG.3.gz $DEBMLOG.4.gz
test -f $DEBMLOG.2.gz && mv $DEBMLOG.2.gz $DEBMLOG.3.gz

SpivEgin

---
# ^^^ YAML documents must begin with the document separator "---"
#
#### Example docblock, I like to put a descriptive comment at the top of my 
#### playbooks.
#
# Overview: Playbook to bootstrap a new host for configuration management.
# Applies to: production
# Description: 
#   Ensures that a host is configured for management with Ansible.

SpivEgin

Internet Scale Services Checklist

A checklist for designing and developing internet scale services, inspired by James Hamilton's 2007 paper "On Desgining and Deploying Internet-Scale Services."

• http://mvdirona.com/jrh/talksandpapers/jamesrh_lisa.pdf

Basic tenets

• Does the design expect failures to happen regularly and handle them gracefully?
• Have we kept things as simple as possible?

SpivEgin

---

# based on https://gist.github.com/briceburg/ded5e82a70e5af71a611

- name: common utilities
  apt:
    name: "{{ item }}"
    state: present
    update_cache: yes
    cache_valid_time: 3600

SpivEgin

vagrant up
vagrant ssh -c "curl -L https://github.com/{your-username}.keys >> /home/vagrant/.ssh/authorized_keys"

SpivEgin

server {

  # Server name 
  server_name example.com;

  # Server Port
  listen 80;

  # Webroot
  root /var/www/;