Vagrant: Add support for Vagrant install (vagrant up)

Cf README, this adds support to install and setup a dev instance through
Vagrant. The Vagrantfile at the root handles the vagrant commands like
`vagrant up`.

Provisioning is done by the shell script `vagrant-provisionning.sh`,
which is a light wrapper around the `create-dev-setup.sh` which does
most of the job using the standard process, but limiting possible
side-effect by ensuring the environment on which the install is
performed is clean.

Based on an Ubuntu precise 12.04 LTS.

scripts/vagrant-provisioning.sh

@@ -0,0 +1,110 @@
+#!/bin/bash -e
+#
+# Copyright (C) 2013 edX <info@edx.org>
+#
+# Authors: Xavier Antoviaque <xavier@antoviaque.org>
+#
+# This software's license gives you freedom; you can copy, convey,
+# propagate, redistribute and/or modify this program under the terms of
+# the GNU Affero General Public License (AGPL) as published by the Free
+# Software Foundation (FSF), either version 3 of the License, or (at your
+# option) any later version of the AGPL published by the FSF.
+#
+# This program is distributed in the hope that it will be useful, but
+# WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU Affero
+# General Public License for more details.
+#
+# You should have received a copy of the GNU Affero General Public License
+# along with this program in a file in the toplevel directory called
+# "AGPLv3".  If not, see <http://www.gnu.org/licenses/>.
+
+
+###############################################################################
+
+# vagrant-provisioning.sh:
+#
+# Script to setup base environment on Vagrant, based on `precise32` image
+# Runs ./scripts/create-dev-env.sh for the actual setup
+#
+# This script is ran by `$ vagrant up`, see the README for more explanations
+
+
+# APT - Packages ##############################################################
+
+apt-get update
+apt-get install -y python-software-properties vim
+
+
+# Curl - No progress bar ######################################################
+
+[[ -f ~vagrant/.curlrc ]] || echo "silent show-error" > ~vagrant/.curlrc
+chown vagrant.vagrant ~vagrant/.curlrc
+
+
+# SSH - Known hosts ###########################################################
+
+# Github
+([[ -f ~vagrant/.ssh/known_hosts ]] && grep "zBX7bKA= ssh" ~vagrant/.ssh/known_hosts) || {
+    echo "|1|4DtBcMsTM4zgl/jTS7h3ZkmS/Vc=|XkRnn2xEhr8ixOxeskJAzBX7bKA= ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ==" >> ~vagrant/.ssh/known_hosts
+}
+([[ -f ~vagrant/.ssh/known_hosts ]] && grep "jO3J5bvw= ssh" ~vagrant/.ssh/known_hosts) || {
+    echo "|1|9rANf/qOAPgKH/TXpGuZCAgGxMs=|x9VYWEDI8kiotbhhNXqjO3J5bvw= ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ==" >> ~vagrant/.ssh/known_hosts
+}
+chown vagrant.vagrant ~vagrant/.ssh/known_hosts
+
+
+# edX - Development environment ###############################################
+
+chown vagrant.vagrant /edx
+
+# For convenience with `vagrant ssh`, the `edx-plateform` virtualenv is always 
+# loaded after the first run, so we need to deactivate that behavior to run
+# `create-dev-env.sh`.
+[[ -f ~vagrant/.bash_profile ]] && {
+    mv ~vagrant/.bash_profile ~vagrant/.bash_profile.bak
+}
+sudo -u vagrant -i bash -c "cd /edx/edx-platform && ./scripts/create-dev-env.sh -ynq"
+
+
+# Virtualenv - Always load ####################################################
+
+([[ -f ~vagrant/.bash_profile ]] && grep "edx-platform/bin/activate" ~vagrant/.bash_profile) || {
+    echo -e "\n. /home/vagrant/.virtualenvs/edx-platform/bin/activate\n" >> ~vagrant/.bash_profile
+}
+
+
+# Directory ###################################################################
+
+grep "cd /edx/edx-platform" ~vagrant/.bash_profile || {
+    echo -e "\ncd /edx/edx-platform\n" >> ~vagrant/.bash_profile
+}
+
+
+# End #########################################################################
+
+cat << EOF
+==============================================================================
+Success!
+==============================================================================
+
+Now, from the virtual machine (connect with "vagrant ssh" if vagrant didn't
+log you in already), you can start Studio & LMS with the following commands:
+
+- Learning management system (LMS):
+    $ rake lms[cms.dev,0.0.0.0:8000]
+
+    =>  http://192.168.20.40:8000/
+
+- Studio: 
+    $ rake cms[dev,0.0.0.0:8001]
+
+    => http://192.168.20.40:8001/
+
+
+See the README for details.
+
+
+EOF
+
+