Deprecated rake functions issue a warning and then call paver
replacements
Bring Paver commands up to date with master for servers, assets, and docs.
Revert deprecation of quality, tests, and i18n for a future pull request.
Deprecate workspace migration
The command built to generate the list of commits committed but not
authored by a particular individual was incorrect, so some commits
were incorrectly omitted in the table as entries belonging to the
committer.
The provisioning script used to check for the existence of the
`/opt/edx/node_modules` folder to decide if the installation has already
been completed. However, since additional instructions were executed
by the installer afterwards, any installation error (eg. download
timeouts on low quality connections) happening between the creation of
that folder and the end of the installation wouldn't be recovered from
on the next vagrant instance boot.
vagrant:
- check actual IP;
- only init machine first time, just as native installations;
- add .bash_profile to permissions fixup;
- cleanup excessive newlines in making .bash_profile;
README:
- include admin & debugging use;
- info about re-initializing VM & manually running create-dev-env.sh;
- add django admin & debug_toolbar setting info
Conflicts:
AUTHORS
scripts/vagrant-provisioning.sh
Some parts of the `create-dev-env/sh` script use `$WORKON_HOME` and
others hardcode `$HOME/.virtualenvs` which means if you **don't** put
your virtualenvs under `$HOME/.virtualenvs`, the script doesn't work at
all.
This commit removes the hardcoding of virtualenv location and
consistently uses `$WORKON_HOME` everywhere.
Yarko's `$BASE` patch has been merged and rewritten since
the original pull request was created, resulting in the `$BASE` being
incorrectly set to the default `/home/vagrant/edx_all` by the new code.
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.
Since the output is passed through tee, when the django admin asks the
user if he would like to create a super user account, it blocks the
install, without even showing the question.
Disabled interactivity for syncdb.
