 |
 |
On 4/6/16 9:49 AM, Annamarie C Klose wrote: > Hi, all, > > Can anyone provide a technical explanation as to why it is not appropriate to install Islandora on a public server with Vagrant? Despite all the documentation instructing that Vagrant is for development only, my university's IT department thinks Vagrant makes Islandora more secure for production use. They have also stated "Vagrant is used to keep dependencies separate on machines in the same way Pythons Virtualenv or Ruby's Docker is." Unfortunately, secure networking is outside of my expertise. I'm concerned that Vagrant's virtualization is a poor substitute for the real thing. Before I add hundreds of records to Islandora, I'd like to make sure that I'm building my library's digital collections on a steady foundation. Any advice and/or explanations to give IT is welcome. If we agree that your University IT are the Operations people find the nicest way to tell them how the developers of Vagrant view the tool below https://www.vagrantup.com/docs/why-vagrant/ Specifically. "...If you are an operations engineer, Vagrant gives you a disposable environment and consistent workflow for developing and testing infrastructure management scripts..." You are also correct in being wary about having a production application running on Vagrant. A part of me wants to test that just for laughs, but it will be painful to set up for them and the performance will horrible for you. Cheers, ./fxk -- "Anyone attempting to generate random numbers by deterministic means is, of course, living in a state of sin." -- John Von Neumann