Hello all, I recently came to know about Vagrant and was impressed about its capabilities and simplifying some of the development workflows. I have started reading more about the same but i need some strategic advice from the more experienced users on this group.
The capability that particularly impresses me is the ability to setup a *single standardized development environment* for all the team members such that when a new member joins they just need to close a repo and issue a vagrant up. My setup and vision is as follows - Host and guest are both Ubuntu 12.04 LTS. - Vagrant with Virtual box. - Intent to use for development only - but to follow and learn practices that are scalable (in case the process needs to be replicated to a team of 100+ not necessarily geo-colocated) - The application would be a Web front end talking to a J2EE backed using RESTful web services. In such a scenario, I would want - only the IDE and the Browser to be running on the host - *such that each developer can have it as per their preference.* - all build tools like maven, maven repo, dependencies, yeoman stack, database, app server should be on the guest- *something which should be standard.* This is the possibility that impresses me the most. I also want the actual build to happen on the guest, which will then get deployed in the app server running in the guest. Is this a practical vision to have ? Any best practices or documents one can guide me towards. Also in such a setup since the entire maven repo and dependencies are in the Guest OS, but I am using Eclipse on the Host OS for editing - how can one assure of code completion and dependency resolution that is important for Eclipse to work too? Awaiting guidance. Ready to be redirected to some reference reading - if that needs to be done first before posting on this forum Thanks for your help. Hemen. -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
