From e8bcf6a035d4e4de1e11ad59dc744bcf010cb874 Mon Sep 17 00:00:00 2001 From: USAMI Kenta Date: Wed, 31 May 2017 12:52:03 +0900 Subject: [PATCH] Explicitly use --provider option for vagrant up When a provider other than virtualbox is registered in Vagrant, `vagrant up` can not start Mastodon. For example, it corresponds to the environment where Parallels Desktop is installed. --- Running-Mastodon/Vagrant-guide.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Running-Mastodon/Vagrant-guide.md b/Running-Mastodon/Vagrant-guide.md index c8e3e63c..dd5b33ce 100644 --- a/Running-Mastodon/Vagrant-guide.md +++ b/Running-Mastodon/Vagrant-guide.md @@ -17,11 +17,11 @@ To create and provision a new virtual machine for Mastodon development run: git clone https://github.com/tootsuite/mastodon.git cd mastodon - vagrant up + vagrant up --provider virtualbox **Note:** On Linux hosts, you will need to [enable NFS support](https://www.vagrantup.com/docs/synced-folders/nfs.html). -Running `vagrant up` for the first time will run provisioning, which will: +Running `vagrant up --provider virtualbox` for the first time will run provisioning, which will: - Download the Ubuntu 14.04 base image, if there isn't already a copy on your machine - Create a new VirtualBox virtual machine from that image @@ -29,7 +29,7 @@ Running `vagrant up` for the first time will run provisioning, which will: ## Starting the server -The Vagrant box will automatically start after provisioning. It can be started in future with `vagrant up` from the mastodon directory. +The Vagrant box will automatically start after provisioning. It can be started in future with `vagrant up --provider virtualbox` from the mastodon directory. To start the application: