Hi, The reason is being able to "see" local git commits inside the VM. The provision script uses the synchronized git directory when deploying (https://gitlab.com/mayan-edms/mayan-edms/blob/master/contrib/scripts/install/development.sh#L24). If you select a branch and do a commit on the host, you can then test that commit on the VM by doing a git pull inside the deployed install (/home/vagrant/mayan). The goal is quick experimentation but on an homogeneous/predictable environment.
No problem at all, this is what this mailing list is for! On Thursday, January 7, 2016 at 3:57:07 PM UTC-4, Rachael Sewell wrote: > > Hello, > > I'm currently using Vagrant for my development environment. I will likely > also use a virtual machine for deployment as well. I had a few questions > regarding the VM. I see that there are two mayan installations: > > 1) /home/vagrant/mayan-edms - this one appears to have already had the > initialsetup and venv created. > 2) /mayan-edms-repository - this one is the directory synchronized to the > host machine. > > What is the reason for the two separate installations? Thanks for being > patient with my novice questions:) > > Rachael > -- --- You received this message because you are subscribed to the Google Groups "Mayan EDMS" 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.
