Vagrant config

db-install.sh

#!/bin/bash

# This provisioning script creates a database server.

echo "##############################"
echo "## Provisioning database VM ##"
echo "##############################"

POSTGRESQL_VERSION="9.3.3"
PROJECT_NAME=VBEZ

# Update the local package index
echo "#######################"
echo "## Updating base box ##"
echo "#######################"
apt-get update -y

# Add dependencies needed for vagrant guest tools
sudo apt-get install -y python-software-properties=0.82.7.7
sudo add-apt-repository ppa:debfx/virtualbox

# Upgrades can cause regressions, so they are not applied here.
# Required upgrades should be specifically applied.

# # # Actually upgrade all packages that can be upgraded
# # apt-get dist-upgrade -y

# Actually upgrade all packages that can be upgraded
# apt-get upgrade -y

# Install python dev packages.
echo "#####################################"
echo "## Installing development packages ##"
echo "#####################################"
# TODO heroku using: https://devcenter.heroku.com/changelog-items/427

echo "## Installing build-essential..."
# build-essential needed to make postgresql.
apt-get install -y build-essential=11.5ubuntu2.1

# Install PostgreSQL
echo "###########################"
echo "## Installing PostgreSQL ##"
echo "###########################"

# Install postgresql dependencies.
echo "## Installing postgresql dependencies..."
apt-get install -y bison=1:2.5.dfsg-2.1
apt-get install -y flex=2.5.35-10ubuntu3

echo "## Installing postgresql version $POSTGRESQL_VERSION"
cd "/home/vagrant"
wget -q "http://ftp.postgresql.org/pub/source/v$POSTGRESQL_VERSION/postgresql-$POSTGRESQL_VERSION.tar.bz2"
tar jxf "postgresql-$POSTGRESQL_VERSION.tar.bz2"
cd "postgresql-$POSTGRESQL_VERSION"

# Install to /usr - which is on the PATH.
./configure --prefix=/usr
make
make install

# Clean up.
cd /vagrant
rm -rf /home/vagrant/postgresql-*

# Initialize postgres DB
useradd -p postgres postgres
mkdir -p /var/pgsql/data
chown postgres /var/pgsql/data
su -c "/usr/bin/initdb -D /var/pgsql/data --locale=en_US.UTF-8 --encoding=UNICODE" postgres
mkdir /var/pgsql/data/log
chown postgres /var/pgsql/data/log

# Set configuration
cp /vagrant/vagrant_data/db/pg_hba.conf /var/pgsql/data/pg_hba.conf
cp /vagrant/vagrant_data/db/postgresql.conf /var/pgsql/data/postgresql.conf

# Start postgres
su -c '/usr/bin/pg_ctl start -l /var/pgsql/data/log/logfile -D /var/pgsql/data' postgres

# Start postgres at boot
sed -i -e 's/exit 0//g' /etc/rc.local
echo "su -c '/usr/bin/pg_ctl start -l /var/pgsql/data/log/logfile -D /var/pgsql/data' postgres" >> /etc/rc.local

# Install memcached
echo "#########################"
echo "## Installing memcache ##"
echo "#########################"
apt-get install -y memcached=1.4.13-0ubuntu2.1
apt-get install -y libmemcached-dev=0.44-1.1build1
cp /vagrant/vagrant_data/db/memcached.conf /etc/memcached.conf
/etc/init.d/memcached restart

# Install redis
echo "######################"
echo "## Installing redis ##"
echo "######################"
apt-get install -y redis-server=2:2.2.12-1build1
cp /vagrant/vagrant_data/db/redis.conf /etc/redis/redis.conf
service redis-server restart

# Remove any packages that are no longer needed
echo "#################################################"
echo "## Removing packages that are no longer needed ##"
echo "#################################################"
apt-get autoremove -y

# Report
echo -e "\nInstalled versions:"
(
  psql --version
) | sed -u "s/^/  /"

echo -e "\nSuccess!"
exit 0

memcached.conf

# memcached default config file
# 2003 - Jay Bonci <jaybonci@debian.org>
# This configuration file is read by the start-memcached script provided as
# part of the Debian GNU/Linux distribution. 

# Run memcached as a daemon. This command is implied, and is not needed for the
# daemon to run. See the README.Debian that comes with this package for more
# information.
-d

# Log memcached's output to /var/log/memcached
logfile /var/log/memcached.log

# Be verbose
# -v

# Be even more verbose (print client commands as well)
# -vv

# Start with a cap of 64 megs of memory. It's reasonable, and the daemon default
# Note that the daemon will grow to this size, but does not start out holding this much
# memory
-m 64

# Default connection port is 11211
-p 11211 

# Run the daemon as root. The start-memcached will default to running as root if no
# -u command is present in this config file
-u memcache

# Specify which IP address to listen on. The default is to listen on all IP addresses
# This parameter is one of the only security measures that memcached has, so make sure
# it's listening on a firewalled interface.
#-l 127.0.0.1

# Limit the number of simultaneous incoming connections. The daemon default is 1024
# -c 1024

# Lock down all paged memory. Consult with the README and homepage before you do this
# -k

# Return error when memory is exhausted (rather than removing items)
# -M

# Maximize core file limit
# -r

pg_hba.conf

local   all             all                                     trust
host    all             all             127.0.0.1/32            trust
host    all             all             192.168.0.0/16          trust
host    all             all             ::1/128                 trust

postgresql.conf

listen_addresses = '*'
port = 5432
max_connections = 100
shared_buffers = 24MB
log_timezone = 'UTC'
datestyle = 'iso, mdy'
timezone = 'UTC'
lc_messages = 'en_US.UTF-8'
lc_monetary = 'en_US.UTF-8'
lc_numeric = 'en_US.UTF-8'
lc_time = 'en_US.UTF-8'
default_text_search_config = 'pg_catalog.english'

redis.conf

# Redis configuration file example

# Note on units: when memory size is needed, it is possible to specifiy
# it in the usual form of 1k 5GB 4M and so forth:
#
# 1k => 1000 bytes
# 1kb => 1024 bytes
# 1m => 1000000 bytes
# 1mb => 1024*1024 bytes
# 1g => 1000000000 bytes
# 1gb => 1024*1024*1024 bytes
#
# units are case insensitive so 1GB 1Gb 1gB are all the same.

# By default Redis does not run as a daemon. Use 'yes' if you need it.
# Note that Redis will write a pid file in /var/run/redis.pid when daemonized.
daemonize yes

# When running daemonized, Redis writes a pid file in /var/run/redis.pid by
# default. You can specify a custom pid file location here.
pidfile /var/run/redis/redis-server.pid

# Accept connections on the specified port, default is 6379.
# If port 0 is specified Redis will not listen on a TCP socket.
port 6379

# If you want you can bind a single interface, if the bind option is not
# specified all the interfaces will listen for incoming connections.
#
# bind 127.0.0.1

# Specify the path for the unix socket that will be used to listen for
# incoming connections. There is no default, so Redis will not listen
# on a unix socket when not specified.
#
# unixsocket /var/run/redis/redis.sock

# Close the connection after a client is idle for N seconds (0 to disable)
timeout 300

# Set server verbosity to 'debug'
# it can be one of:
# debug (a lot of information, useful for development/testing)
# verbose (many rarely useful info, but not a mess like the debug level)
# notice (moderately verbose, what you want in production probably)
# warning (only very important / critical messages are logged)
loglevel notice

# Specify the log file name. Also 'stdout' can be used to force
# Redis to log on the standard output. Note that if you use standard
# output for logging but daemonize, logs will be sent to /dev/null
logfile /var/log/redis/redis-server.log

# To enable logging to the system logger, just set 'syslog-enabled' to yes,
# and optionally update the other syslog parameters to suit your needs.
# syslog-enabled no

# Specify the syslog identity.
# syslog-ident redis

# Specify the syslog facility.  Must be USER or between LOCAL0-LOCAL7.
# syslog-facility local0

# Set the number of databases. The default database is DB 0, you can select
# a different one on a per-connection basis using SELECT <dbid> where
# dbid is a number between 0 and 'databases'-1
databases 16

################################ SNAPSHOTTING  #################################
#
# Save the DB on disk:
#
#   save <seconds> <changes>
#
#   Will save the DB if both the given number of seconds and the given
#   number of write operations against the DB occurred.
#
#   In the example below the behaviour will be to save:
#   after 900 sec (15 min) if at least 1 key changed
#   after 300 sec (5 min) if at least 10 keys changed
#   after 60 sec if at least 10000 keys changed
#
#   Note: you can disable saving at all commenting all the "save" lines.

save 900 1
save 300 10
save 60 10000

# Compress string objects using LZF when dump .rdb databases?
# For default that's set to 'yes' as it's almost always a win.
# If you want to save some CPU in the saving child set it to 'no' but
# the dataset will likely be bigger if you have compressible values or keys.
rdbcompression yes

# The filename where to dump the DB
dbfilename dump.rdb

# The working directory.
#
# The DB will be written inside this directory, with the filename specified
# above using the 'dbfilename' configuration directive.
# 
# Also the Append Only File will be created inside this directory.
# 
# Note that you must specify a directory here, not a file name.
dir /var/lib/redis

################################# REPLICATION #################################

# Master-Slave replication. Use slaveof to make a Redis instance a copy of
# another Redis server. Note that the configuration is local to the slave
# so for example it is possible to configure the slave to save the DB with a
# different interval, or to listen to another port, and so on.
#
# slaveof <masterip> <masterport>

# If the master is password protected (using the "requirepass" configuration
# directive below) it is possible to tell the slave to authenticate before
# starting the replication synchronization process, otherwise the master will
# refuse the slave request.
#
# masterauth <master-password>

# When a slave lost the connection with the master, or when the replication
# is still in progress, the slave can act in two different ways:
#
# 1) if slave-serve-stale-data is set to 'yes' (the default) the slave will
#    still reply to client requests, possibly with out of data data, or the
#    data set may just be empty if this is the first synchronization.
#
# 2) if slave-serve-stale data is set to 'no' the slave will reply with
#    an error "SYNC with master in progress" to all the kind of commands
#    but to INFO and SLAVEOF.
#
slave-serve-stale-data yes

################################## SECURITY ###################################

# Require clients to issue AUTH <PASSWORD> before processing any other
# commands.  This might be useful in environments in which you do not trust
# others with access to the host running redis-server.
#
# This should stay commented out for backward compatibility and because most
# people do not need auth (e.g. they run their own servers).
# 
# Warning: since Redis is pretty fast an outside user can try up to
# 150k passwords per second against a good box. This means that you should
# use a very strong password otherwise it will be very easy to break.
#
# requirepass foobared

# Command renaming.
#
# It is possilbe to change the name of dangerous commands in a shared
# environment. For instance the CONFIG command may be renamed into something
# of hard to guess so that it will be still available for internal-use
# tools but not available for general clients.
#
# Example:
#
# rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52
#
# It is also possilbe to completely kill a command renaming it into
# an empty string:
#
# rename-command CONFIG ""

################################### LIMITS ####################################

# Set the max number of connected clients at the same time. By default there
# is no limit, and it's up to the number of file descriptors the Redis process
# is able to open. The special value '0' means no limits.
# Once the limit is reached Redis will close all the new connections sending
# an error 'max number of clients reached'.
#
# maxclients 128

# Don't use more memory than the specified amount of bytes.
# When the memory limit is reached Redis will try to remove keys with an
# EXPIRE set. It will try to start freeing keys that are going to expire
# in little time and preserve keys with a longer time to live.
# Redis will also try to remove objects from free lists if possible.
#
# If all this fails, Redis will start to reply with errors to commands
# that will use more memory, like SET, LPUSH, and so on, and will continue
# to reply to most read-only commands like GET.
#
# WARNING: maxmemory can be a good idea mainly if you want to use Redis as a
# 'state' server or cache, not as a real DB. When Redis is used as a real
# database the memory usage will grow over the weeks, it will be obvious if
# it is going to use too much memory in the long run, and you'll have the time
# to upgrade. With maxmemory after the limit is reached you'll start to get
# errors for write operations, and this may even lead to DB inconsistency.
#
# maxmemory <bytes>

# MAXMEMORY POLICY: how Redis will select what to remove when maxmemory
# is reached? You can select among five behavior:
# 
# volatile-lru -> remove the key with an expire set using an LRU algorithm
# allkeys-lru -> remove any key accordingly to the LRU algorithm
# volatile-random -> remove a random key with an expire set
# allkeys->random -> remove a random key, any key
# volatile-ttl -> remove the key with the nearest expire time (minor TTL)
# noeviction -> don't expire at all, just return an error on write operations
# 
# Note: with all the kind of policies, Redis will return an error on write
#       operations, when there are not suitable keys for eviction.
#
#       At the date of writing this commands are: set setnx setex append
#       incr decr rpush lpush rpushx lpushx linsert lset rpoplpush sadd
#       sinter sinterstore sunion sunionstore sdiff sdiffstore zadd zincrby
#       zunionstore zinterstore hset hsetnx hmset hincrby incrby decrby
#       getset mset msetnx exec sort
#
# The default is:
#
# maxmemory-policy volatile-lru

# LRU and minimal TTL algorithms are not precise algorithms but approximated
# algorithms (in order to save memory), so you can select as well the sample
# size to check. For instance for default Redis will check three keys and
# pick the one that was used less recently, you can change the sample size
# using the following configuration directive.
#
# maxmemory-samples 3

############################## APPEND ONLY MODE ###############################

# By default Redis asynchronously dumps the dataset on disk. If you can live
# with the idea that the latest records will be lost if something like a crash
# happens this is the preferred way to run Redis. If instead you care a lot
# about your data and don't want to that a single record can get lost you should
# enable the append only mode: when this mode is enabled Redis will append
# every write operation received in the file appendonly.aof. This file will
# be read on startup in order to rebuild the full dataset in memory.
#
# Note that you can have both the async dumps and the append only file if you
# like (you have to comment the "save" statements above to disable the dumps).
# Still if append only mode is enabled Redis will load the data from the
# log file at startup ignoring the dump.rdb file.
#
# IMPORTANT: Check the BGREWRITEAOF to check how to rewrite the append
# log file in background when it gets too big.

appendonly no

# The name of the append only file (default: "appendonly.aof")
# appendfilename appendonly.aof

# The fsync() call tells the Operating System to actually write data on disk
# instead to wait for more data in the output buffer. Some OS will really flush 
# data on disk, some other OS will just try to do it ASAP.
#
# Redis supports three different modes:
#
# no: don't fsync, just let the OS flush the data when it wants. Faster.
# always: fsync after every write to the append only log . Slow, Safest.
# everysec: fsync only if one second passed since the last fsync. Compromise.
#
# The default is "everysec" that's usually the right compromise between
# speed and data safety. It's up to you to understand if you can relax this to
# "no" that will will let the operating system flush the output buffer when
# it wants, for better performances (but if you can live with the idea of
# some data loss consider the default persistence mode that's snapshotting),
# or on the contrary, use "always" that's very slow but a bit safer than
# everysec.
#
# If unsure, use "everysec".

# appendfsync always
appendfsync everysec
# appendfsync no

# When the AOF fsync policy is set to always or everysec, and a background
# saving process (a background save or AOF log background rewriting) is
# performing a lot of I/O against the disk, in some Linux configurations
# Redis may block too long on the fsync() call. Note that there is no fix for
# this currently, as even performing fsync in a different thread will block
# our synchronous write(2) call.
#
# In order to mitigate this problem it's possible to use the following option
# that will prevent fsync() from being called in the main process while a
# BGSAVE or BGREWRITEAOF is in progress.
#
# This means that while another child is saving the durability of Redis is
# the same as "appendfsync none", that in pratical terms means that it is
# possible to lost up to 30 seconds of log in the worst scenario (with the
# default Linux settings).
# 
# If you have latency problems turn this to "yes". Otherwise leave it as
# "no" that is the safest pick from the point of view of durability.
no-appendfsync-on-rewrite no

################################ VIRTUAL MEMORY ###############################

# Virtual Memory allows Redis to work with datasets bigger than the actual
# amount of RAM needed to hold the whole dataset in memory.
# In order to do so very used keys are taken in memory while the other keys
# are swapped into a swap file, similarly to what operating systems do
# with memory pages.
#
# To enable VM just set 'vm-enabled' to yes, and set the following three
# VM parameters accordingly to your needs.

vm-enabled no
# vm-enabled yes

# This is the path of the Redis swap file. As you can guess, swap files
# can't be shared by different Redis instances, so make sure to use a swap
# file for every redis process you are running. Redis will complain if the
# swap file is already in use.
#
# The best kind of storage for the Redis swap file (that's accessed at random) 
# is a Solid State Disk (SSD).
#
# *** WARNING *** if you are using a shared hosting the default of putting
# the swap file under /tmp is not secure. Create a dir with access granted
# only to Redis user and configure Redis to create the swap file there.
vm-swap-file /var/lib/redis/redis.swap

# vm-max-memory configures the VM to use at max the specified amount of
# RAM. Everything that deos not fit will be swapped on disk *if* possible, that
# is, if there is still enough contiguous space in the swap file.
#
# With vm-max-memory 0 the system will swap everything it can. Not a good
# default, just specify the max amount of RAM you can in bytes, but it's
# better to leave some margin. For instance specify an amount of RAM
# that's more or less between 60 and 80% of your free RAM.
vm-max-memory 0

# Redis swap files is split into pages. An object can be saved using multiple
# contiguous pages, but pages can't be shared between different objects.
# So if your page is too big, small objects swapped out on disk will waste
# a lot of space. If you page is too small, there is less space in the swap
# file (assuming you configured the same number of total swap file pages).
#
# If you use a lot of small objects, use a page size of 64 or 32 bytes.
# If you use a lot of big objects, use a bigger page size.
# If unsure, use the default :)
vm-page-size 32

# Number of total memory pages in the swap file.
# Given that the page table (a bitmap of free/used pages) is taken in memory,
# every 8 pages on disk will consume 1 byte of RAM.
#
# The total swap size is vm-page-size * vm-pages
#
# With the default of 32-bytes memory pages and 134217728 pages Redis will
# use a 4 GB swap file, that will use 16 MB of RAM for the page table.
#
# It's better to use the smallest acceptable value for your application,
# but the default is large in order to work in most conditions.
vm-pages 134217728

# Max number of VM I/O threads running at the same time.
# This threads are used to read/write data from/to swap file, since they
# also encode and decode objects from disk to memory or the reverse, a bigger
# number of threads can help with big objects even if they can't help with
# I/O itself as the physical device may not be able to couple with many
# reads/writes operations at the same time.
#
# The special value of 0 turn off threaded I/O and enables the blocking
# Virtual Memory implementation.
vm-max-threads 4

############################### ADVANCED CONFIG ###############################

# Hashes are encoded in a special way (much more memory efficient) when they
# have at max a given numer of elements, and the biggest element does not
# exceed a given threshold. You can configure this limits with the following
# configuration directives.
hash-max-zipmap-entries 512
hash-max-zipmap-value 64

# Similarly to hashes, small lists are also encoded in a special way in order
# to save a lot of space. The special representation is only used when
# you are under the following limits:
list-max-ziplist-entries 512
list-max-ziplist-value 64

# Sets have a special encoding in just one case: when a set is composed
# of just strings that happens to be integers in radix 10 in the range
# of 64 bit signed integers.
# The following configuration setting sets the limit in the size of the
# set in order to use this special memory saving encoding.
set-max-intset-entries 512

# Active rehashing uses 1 millisecond every 100 milliseconds of CPU time in
# order to help rehashing the main Redis hash table (the one mapping top-level
# keys to values). The hash table implementation redis uses (see dict.c)
# performs a lazy rehashing: the more operation you run into an hash table
# that is rhashing, the more rehashing "steps" are performed, so if the
# server is idle the rehashing is never complete and some more memory is used
# by the hash table.
# 
# The default is to use this millisecond 10 times every second in order to
# active rehashing the main dictionaries, freeing memory when possible.
#
# If unsure:
# use "activerehashing no" if you have hard latency requirements and it is
# not a good thing in your environment that Redis can reply form time to time
# to queries with 2 milliseconds delay.
#
# use "activerehashing yes" if you don't have such hard requirements but
# want to free memory asap when possible.
activerehashing yes

################################## INCLUDES ###################################

# Include one or more other config files here.  This is useful if you
# have a standard template that goes to all redis server but also need
# to customize a few per-server settings.  Include files can include
# other files, so use this wisely.
#
# include /path/to/local.conf
# include /path/to/other.conf

Vagrantfile

# This configuration will set up a database (db) and a web server (web) VM.

# Assumes the use of VirtualBox 4.3.14-95030 as a provider.
# Uses vagrant-vbguest plugin (https://github.com/dotless-de/vagrant-vbguest)
# to keep VirtualBox Guest Addition wrangled.

# Configuration

# Machine-specific configuration
DB_INSTALL_SCRIPT = "vagrant_data/db/install.sh"
DB_IP  = "192.168.50.3"
WEB_INSTALL_SCRIPT = "vagrant_data/web/install.sh"
WEB_IP = "192.168.50.4"

# General configuration

# CPUs per machine
CPUS = "1"

# Memory per machine - set to 512MB to match Heroku limits.
MEMORY = "512"

PROVIDER = "virtualbox"
SYNCED_FOLDER = "/vagrant"
VM_BOX = "hashicorp/precise64"
VM_BOX_VERSION = "1.1.0"
VAGRANTFILE_API_VERSION = "2"

# Lock down vagrant version.
Vagrant.require_version ">= 1.6.3"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
  config.vbguest.no_install = false

  # Lock box version down
  config.vm.box = VM_BOX
  config.vm.box_version = VM_BOX_VERSION
  config.vm.box_check_update = true
  config.vm.synced_folder ".", SYNCED_FOLDER, type: "nfs"

  # Start with the database server (db):
  config.vm.define :"db" do |db|
    db.vm.hostname = "db"
    db.vm.provision :shell, :path => DB_INSTALL_SCRIPT
    db.vm.network :private_network, ip: DB_IP

    # Set up VM
    db.vm.provider PROVIDER do |v|
      v.customize [
        "modifyvm", :id,
        "--memory", MEMORY,
        "--cpus", CPUS
      ]
    end
  end

  # And now the web server (web):
  config.vm.define :"web", primary: true do |web|
    web.vm.hostname = "web"
    web.vm.provision :shell, :path => WEB_INSTALL_SCRIPT
    web.vm.network :private_network, ip: WEB_IP

    # Set up VM
    web.vm.provider PROVIDER do |v|
      v.customize [
        "modifyvm", :id,
        "--memory", MEMORY,
        "--cpus", CPUS
      ]
    end
  end
end

web-install.sh

#!/bin/bash

# This provisioning script creates a web server.
echo "#########################"
echo "## Provisioning web VM ##"
echo "#########################"

NODE_VERSION="0.10.28"
POSTGRESQL_VERSION="9.3.3"

# If the python version is changed, but sure to update the virtualenv's usage
# and the heroku runtime used.
PYTHON_VERSION="2.7.7"
PROJECT_NAME=VBEZ

# Update the local package index.
echo "#######################"
echo "## Updating base box ##"
echo "#######################"
apt-get update -y
sudo apt-get install -y python-software-properties=0.82.7.7
sudo add-apt-repository ppa:debfx/virtualbox

# Upgrades can cause regressions, so they are not applied here.
# Required upgrades should be specifically applied.

# # # Actually upgrade all packages that can be upgraded
# # apt-get dist-upgrade -y

# Actually upgrade all packages that can be upgraded
# apt-get upgrade -y

# Install git and mercurial.
echo "######################"
echo "## Installing DVCSs ##"
echo "######################"

echo "## Installing git..."
apt-get install -y git=1:1.7.9.5-1

echo "## Installing mercurial..."
apt-get install -y mercurial=2.0.2-1ubuntu1

# Install python dev packages.
echo "#####################################"
echo "## Installing development packages ##"
echo "#####################################"
# TODO heroku using: https://devcenter.heroku.com/changelog-items/427

# build-essential for make, etc.
apt-get install -y build-essential=11.5ubuntu2.1

# libbz2-dev for gzip.
apt-get install -y libbz2-dev=1.0.6-1

# libncurses5-dev for nose-progressive
apt-get install -y libncurses5-dev=5.9-4

# libjpeg-dev for Pillow
apt-get install -y libjpeg-dev=8c-2ubuntu7

# Install curl for downloading.
echo "## Installng curl for downloading tools..."
sudo apt-get install -y curl=7.22.0-3ubuntu4.8

echo "## Installing base python..."
apt-get install -y python=2.7.3-0ubuntu2.2

echo "## Installing python-dev..."
apt-get install -y python-dev=2.7.3-0ubuntu2.2

echo "## Installing python-setuptools..."
apt-get install -y python-setuptools=0.6.24-1ubuntu1

echo "## Installing python-pip..."
apt-get install -y python-pip=1.0-1build1

echo "## Upgrading pip..."
sudo pip install --upgrade pip==1.5.6

echo "## Getting python version $PYTHON_VERSION..."
cd /home/vagrant
curl "https://www.python.org/ftp/python/$PYTHON_VERSION/Python-$PYTHON_VERSION.tgz" | tar xz

echo "## Building python $PYTHON_VERSION..."
cd "/home/vagrant/Python-$PYTHON_VERSION"

# --enable-shared used by heroku
# --enable-unicode=uc4 needed for virtualenv
./configure --enable-shared --enable-unicode=ucs4 --prefix=/usr/local
make
make altinstall

# Clean up.
cd /vagrant
rm -rf /home/vagrant/Python-*

# Add the new python shared libary to the search path.
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib
export LD_LIBRARY_PATH

# Install PostgreSQL.
echo "###########################"
echo "## Installing PostgreSQL ##"
echo "###########################"

# Install postgresql dependencies.
echo "## Installing postgresql dependencies..."
apt-get install -y bison=1:2.5.dfsg-2.1
apt-get install -y flex=2.5.35-10ubuntu3

# Install postgresql.
echo "## Installing postgresql version $POSTGRESQL_VERSION"
cd "/home/vagrant"
wget -q "http://ftp.postgresql.org/pub/source/v$POSTGRESQL_VERSION/postgresql-$POSTGRESQL_VERSION.tar.bz2"
tar jxf "postgresql-$POSTGRESQL_VERSION.tar.bz2"
cd "postgresql-$POSTGRESQL_VERSION"

# Install to /usr - which is on the PATH.
./configure --prefix=/usr

# Make client only
make -C src/bin install
make -C src/include install
make -C src/interfaces install
make -C doc install

# Clean up.
cd /vagrant
rm -rf /home/vagrant/postgresql-*

# Install libmemcached-dev for client use.
echo "########################################"
echo "## Installing memcache for client use ##"
echo "########################################"
apt-get install -y libmemcached-dev=0.44-1.1build1

# Install redis (just need redis-cli).
echo "######################"
echo "## Installing redis ##"
echo "######################"
apt-get install -y redis-server=2:2.2.12-1build1
service redis-server stop

# Install heroku toolbelt.  Unfortunately, cannot seem to pin the version.
echo "################################"
echo "## Installing heroku toolbelt ##"
echo "################################"
# TODO find a way to pin the toolbelt version.
wget -qO- https://toolbelt.heroku.com/install-ubuntu.sh | sh

# Install tesseract (OCR) and ghostscript.
echo "##################################################"
echo "## Installing tesseract and ghostscript for OCR ##"
echo "##################################################"
apt-get install -y tesseract-ocr=3.02.01-2
apt-get install -y ghostscript=9.05~dfsg-0ubuntu4.2

# Install npm.
echo "#####################"
echo "## Installing node ##"
echo "#####################"
# From https://gist.github.com/isaacs/579814

# Install node.  npm comes with node now.
echo "## Installing node version $NODE_VERSION"
# mkdir ~vagrant/local
mkdir "/home/vagrant/$NODE_VERSION"
cd "/home/vagrant/$NODE_VERSION"
curl "http://nodejs.org/dist/v$NODE_VERSION/node-v$NODE_VERSION.tar.gz" | tar xz --strip-components=1
./configure --prefix=/usr
make install

# Clean up.
cd /vagrant
rm -rf "/home/vagrant/$NODE_VERSION"

echo "####################################"
echo "## Installing global npm packages ##"
echo "####################################"
npm install -g bower@1.3.5
npm install -g coffeegulp@0.0.4
npm install -g coffee-script@1.7.1
npm install -g npm@1.4.14
npm install -g npm-check-updates@1.2.0
npm install -g requirejs@2.1.14
npm install -g yuglify@0.1.4

echo "#####################"
echo "## Installing gems ##"
echo "#####################"
gem install sass -v 3.3.8

echo "###########################"
echo "## Installing virtualenv ##"
echo "###########################"
/usr/local/bin/pip install virtualenv==1.11.6
/usr/local/bin/pip install virtualenvwrapper==4.3
echo "source /usr/local/bin/virtualenvwrapper.sh" >> ~vagrant/.bashrc
#
echo "##########################################"
echo "## Creating a virualenv for the project ##"
echo "##########################################"
source /usr/local/bin/virtualenvwrapper.sh
WORKON_HOME=~vagrant/.virtualenvs

# Change the python runtime used by the virtualenv here:
mkvirtualenv -a /vagrant -p /usr/local/bin/python2.7 -r /vagrant/requirements.txt $PROJECT_NAME

chown -R vagrant:vagrant ~vagrant/.virtualenvs
echo "source /vagrant/config/env" >> ~vagrant/.virtualenvs/$PROJECT_NAME/bin/postactivate
echo "workon $PROJECT_NAME" >> ~vagrant/.bashrc

# Remove any packages that are no longer needed
echo "#################################################"
echo "## Removing packages that are no longer needed ##"
echo "#################################################"
apt-get autoremove -y

# Report
echo -e "\nInstalled versions:"
(
  git --version
  psql --version
  python --version
  ruby --version
) | sed -u "s/^/  /"

echo -e "\nSuccess!"
exit 0