That want be practical. I know what Joel is trying to do because that exactly what I do. The point is to have the code synced immediately as soon as you change it so that you can test it/run it before committing it. As I mentioned it's not that easy to use such a workflow on windows, whether windows is the host or the guest because of the NFS limitation.
On Sun, 1 Mar 2015 at 22:45 Alvaro Miranda Aguilera <[email protected]> wrote: > What about having all on GIT, and as provision do a git clone.. > > and then, the ide access the code remotely by ssh/ftp ? > > On Sun, Mar 1, 2015 at 6:45 AM, Joel Collins <[email protected]> wrote: > > Thanks for the reply Debo. I've been investigating some more and wanted > to > > follow up with some more general findings. > > > > My thinking is that I need our entire document root available on the > host so > > that the IDE can be on the host. So I have been experimenting with > placing > > the entire document root inside a shared folder in vagrant. While I > agree > > that there are other things I could do to improve performance like adding > > more ram, use SSD, etc, I'm leaving all those variables constant for now > and > > just comparing the different file systems. Some performance numbers: > > > > (native, no shared folders, all files live inside the guest) 1.3 secs / > page > > (nfs shared folder) - 3-5 secs / page > > (vboxsf) - 10-15 secs / page > > > > While NFS does seem to work somewhat acceptably, its a real pain because > I > > use windows hosts (I got this to work with the winnfsd vagrant plugin) > and > > it seems buggy (I had to manually kill winnfsd.exe for vagrant up to > work a > > second time), and just overall harder to setup than native shared > folders. > > > > I have a few follow up questions: > > > > Is my assumption that for the IDE to run on the host the entire doc root > > should live on the host correct? I suppose the files could live on the > > guest and the IDE on the host could somehow access the files on the guest > > (NFS the other direction? windows doesn't natively support nfs > > unfortunately, right?) > > Is trying to use vmware + vmware provider + vmware shared folders likely > to > > have comparable performance to NFS? I'm hesitant to pay the $80 for the > > vagrant vmware provider to test this out and I had a lot of trouble > setting > > up the virtual machine in vmware manually without vagrant's assistance. > > > > Thanks again, this forum is amazingly helpful. > > > > On Thursday, February 26, 2015 at 5:23:29 PM UTC-5, _debo wrote: > >> > >> Hi Joel, > >> > >> I think the problem or "bottleneck"is not the combination vagrant + > vbox + > >> NFS. I used to run the very same setup on large scale Magento projects > with > >> decent results. > >> The code was shared between host and guest via NFS. To me it sounds more > >> like a a lack of resources in the VM. In my setup all the VMs had about > 2Gb > >> of RAM split between varnish, apache and mysql say 25/25/50. Of course > you > >> have to make sure the host machine has the actual resources to do so. > >> Moreover SSDs can boost performance and they are a very affordable > >> improvement and good value for money if you don't have them yet. > >> > >> I hope it helps. > >> > >> Cheers, > >> Debo > >> > >> > >> > >> On Thu Feb 26 2015 at 22:11:18 Joel Collins <[email protected]> wrote: > >>> > >>> I'm not sure if this is a vagrant or just general virtualbox/vmware/etc > >>> question, but here goes. We use drupal with lots of contrib modules, > with a > >>> 100mb codebase and ~20k files. I was trying to create a virtual > machine > >>> that has only the stuff necessary to run drupal and let each developer > use > >>> the tools on their host (like, an IDE) in order to do their > development. > >>> Therefore, I wanted the codebase to be shared between the guest and > host (i > >>> think, unless you can show me the light here). > >>> > >>> Our challenge is performance is already not great (1-3 secs / page) > even > >>> on native virtualbox. Sharing the codebase between guests and host > resulted > >>> in unacceptable performance in every configuration I tried (NFS, > etc). I > >>> tried setting up rsync and it seemed to take forever to identify a file > >>> change and sync it across as well. > >>> > >>> I feel I must be missing something here. Is there no way to use a > >>> vagrant-like development workflow with the development tools on a host > >>> machine if the codebase is large? Is there a way to have the files > reside > >>> natively on the guest and use (NFS?) to access the files from the > guest (do > >>> common IDE's support this?)? Should I just bundle an IDE directly in > the > >>> guest? > >>> > >>> I feel like I'm missing some major mental piece here. > >>> > >>> Thanks! > >>> > >>> -- > >>> 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. > > > > -- > > 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. > > -- > 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. > -- 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.
