Virtualized environments
My boss wants me to create a standardized virtual development environment for our company.
This environment should consist mainly of Eclipse (Kepler) with a fairly specific plugin. He claimed Vagrant to be one of the tools we could use to achieve this goal.
Our needs are more geared towards the actual developing process instead of the process of software deployment. What Vagrant seems to be built for is emulating a developement environment in the sense of hosting stuff like apache, and managing the specific dependencies different projects need.
Our needs are different - What my boss wants is to create a complete virtual work environment where developers connect to a remote server and find themselves in a linux GUI like KDE or Xfce. For this task, Vagrant seems to be not very well suited.
I eventually managed to get this to work with the help of Xming, Virtual Box and Vagrant. However the solution does not work very well, since the emulated work environment is running quite slowly.
My question is, is Vagrant even geared towards transferring the whole development process (including! writing the code) into the Virtual Boxes it creates, or is Vagrant geared towards local development while the Virtual Boxes take up the role of stuff like an apache webserver?
I realized this question was pretty "broad" but as I'm just getting started with virtual development environments, I felt the available documentation for Vagrant was lacking.
Thanks in advance
Vagrant is a good choice: it's just a command line front-end for a VM.
Start from an Ubuntu Image, provision it to install what you need through the command line, then package it with vagrant package .
If you absolutely need the GUI for provisioning, add:
xhost +
your host's .bashrc , and you can run eclipse on the guest.
The people who will use your box will also need to add xhost + to their .bashrc . Or you could give them a magic script that does xhost + && vagrant up && vagrant ssh -c eclipse .
上一篇: Vbox / Vagrant无法启动虚拟机，我无法打开控制台
下一篇: 虚拟化环境