Bureaucrats, confirmed, Administrators
4,558
edits
MediaWiki-Vagrant: Difference between revisions
From Freephile Wiki
Adds links
(adds resources) |
(Adds links) |
||
| Line 14: | Line 14: | ||
There is [http://www.iheavy.com/2014/01/16/how-to-deploy-on-amazon-ec2-with-vagrant/ this article] that explains how to do this, but I didn't want to create a separate VagrantFile. After not succeeding, I should probably go back and try that approach. | There is [http://www.iheavy.com/2014/01/16/how-to-deploy-on-amazon-ec2-with-vagrant/ this article] that explains how to do this, but I didn't want to create a separate VagrantFile. After not succeeding, I should probably go back and try that approach. | ||
Using multiple providers (AWS, Rackspace, VirtualBox, VMWare) ''with the same virtual machine'' is not a feature of Vagrant. Supposedly this limitation will be removed in a future version of Vagrant. But there is a work-around that you can use to accomplish this -- by creating a multi-machine environment. We are describing that work-around. There are some "cheap" solutions that tell you to either delete, or rename the hidden <code>.virtualbox</code> directory in your project source. Don't do that. That's just deleting the information that you'd need for using the existing provider. Or, only do that if you are trying to permanently switch the provider used in your project -- which is not the case here. To get a fully compatible MediaWiki-Vagrant setup that works for both localhost VirtualBox deployments and cloud Amazon AWS deployments, then read on. | Using multiple [http://docs.vagrantup.com/v2/plugins/providers.html providers] (AWS, Rackspace, VirtualBox, VMWare) ''with the same virtual machine'' is not a feature of Vagrant. Supposedly this limitation will be removed in a future version of Vagrant. But there is a work-around that you can use to accomplish this -- by creating a multi-machine environment. We are describing that work-around. There are some "cheap" solutions that tell you to either delete, or rename the hidden <code>.virtualbox</code> directory in your project source. Don't do that. That's just deleting the information that you'd need for using the existing provider. Or, only do that if you are trying to permanently switch the provider used in your project -- which is not the case here. To get a fully compatible MediaWiki-Vagrant setup that works for both localhost VirtualBox deployments and cloud Amazon AWS deployments, then read on. | ||
=== Caveats === | === Caveats === | ||
The MediaWiki-Vagrant setup is designed for local development and NOT for security, so it may not be suitable for running in the cloud. | The MediaWiki-Vagrant setup is designed for local development and NOT for security, so it may not be suitable for running in the cloud. | ||
The MediaWiki-Vagrant box is setup with NFS shares. The Vagrant-aws plugin has nominal support for shared folders using rsync, so sharing the ~/vagrant folder might work, but it's unkown how well this works. And it's unknown how to disable the | The MediaWiki-Vagrant box is setup with NFS shares. The Vagrant-aws plugin has nominal support for shared folders using rsync, so sharing the ~/vagrant folder might work, but it's unkown how well this works. And it's unknown exactly how to disable the [http://docs.vagrantup.com/v2/synced-folders/basic_usage.html synced folders] in <code>Vagrantfile-extra.rb</code> that is defined in the Vagrantfile | ||
=== Pre-requisites === | === Pre-requisites === | ||
| Line 194: | Line 194: | ||
== Resources == | == Resources == | ||
[https://github.com/mitchellh/vagrant/issues/2733 This is the official 'response'] to this issue. It offers a [https://gist.github.com/maxlinc/8c64c5e93734a3c939b8 gist] that supposedly addresses the problem of running multiple providers, but I wasn't able to figure out how to apply that to the MediaWiki-Vagrant setup. | |||
There is a somewhat related issue in Phabricator that requests a web front-end to make deployment easier. | There is a somewhat related issue in Phabricator that requests a web front-end to make deployment easier. | ||
