barish Posted October 5, 2020 Share Posted October 5, 2020 I followed the documentation and cloned the repo in the Host first, changed to config/templates and started the Vagrant virtual machine. If I am not mistaken, inside the Guest, the repo is cloned again for the actual development. This implies that cloning on the Host system has only the purpose to provide config/templates/Vagrantfile and config-vagrant.conf, is that right? All other cloned files on the HOST have no relevance (except for the directories userpatches and output, which are mounted)? I find that quite confusing and if I am right with my assumption, I would like to add a note to the documentation for future users. Or: Would it be possible to mount the whole repo to the Guest? Link to comment Share on other sites More sharing options...
barish Posted October 8, 2020 Author Share Posted October 8, 2020 Could one of the experienced developers advise me please, if I am right with my above assumption? I don't want to make an unnecessary PR for the documentation, if I haven't understood correctly the process. Link to comment Share on other sites More sharing options...
Igor Posted October 8, 2020 Share Posted October 8, 2020 Vagrant way is kind of "community supported". We mainly don't use this method - native and Docker. Personally - I only tried once and failed. Link to comment Share on other sites More sharing options...
Recommended Posts