vagrant: Graciously fail when vagrant user can't write to /srv/zulip.

Fixes #1410.
This commit is contained in:
Puneeth Chaganti 2018-03-19 10:45:12 +05:30 committed by Tim Abbott
parent 7929bf5c76
commit 7bda069ced
1 changed files with 13 additions and 0 deletions

13
Vagrantfile vendored
View File

@ -191,6 +191,19 @@ export SKIP_VENV_SHELL_WARNING=1
# message after a successful run. # message after a successful run.
set +x set +x
# Check if the zulip directory is writable
if [ ! -w /srv/zulip ]; then
echo "The vagrant user is unable to write to the zulip directory."
echo "To fix this, run the following commands on the host machine:"
# sudo is required since our uid is not 1000
echo ' vagrant halt -f'
echo ' rm -rf /PATH/TO/ZULIP/CLONE/.vagrant'
echo ' sudo chown -R 1000:$(whoami) /PATH/TO/ZULIP/CLONE'
echo "Replace /PATH/TO/ZULIP/CLONE with the path to where zulip code is cloned."
echo "You can resume setting up your vagrant environment by running:"
echo " vagrant up"
exit 1
fi
# Provision the development environment # Provision the development environment
ln -nsf /srv/zulip ~/zulip ln -nsf /srv/zulip ~/zulip
/srv/zulip/tools/provision /srv/zulip/tools/provision