Thanks Brian! This looks like exactly what we need. On Fri, Jan 4, 2019 at 4:54 PM Brian Bouterse <bbout...@redhat.com> wrote:
> pulplift itself relies heavily on "forklift" which itself has some good > docs. Take a look at these docs and see if it generates new questions. > > https://github.com/theforeman/forklift#using-sshfs-to-share-folders > https://github.com/theforeman/forklift#adding-custom-boxes > > > On Fri, Jan 4, 2019 at 4:49 PM Dennis Kliban <dkli...@redhat.com> wrote: > >> We currently use Vagrant directly to create our development >> environment[0]. I would like to be able to use pulplift to create a >> development environment for Pulp 3. Our current Vagrantfile uses SSHFS to >> mount source code on the host onto the vagrant box[1]. This allows >> developers to make changes locally on their laptop and the same code to run >> inside the vagrant box. >> >> pulplift already provides boxes named 'pulp3-source-*'. These boxes use a >> playbook[2] from ansible-pulp3 repo to perform the installation. By >> default, this playbook assumes that the vagrant box has pulp source code at >> "/home/vagrant/devel/pulp". However, without the synced folders, the >> source code is not there and the install fails. >> >> I would like to extend pulplift to use synced folders for the source >> install boxes. However, I am not sure where to add such directives for >> vagrant. >> >> Eric, can you point me in the right direction? >> >> >> [0] https://github.com/pulp/devel/blob/master/Vagrantfile.example >> [1] https://github.com/pulp/devel/blob/master/Vagrantfile.example#L8 >> [2] https://github.com/pulp/ansible-pulp3/blob/master/source-install.yml >> >> _______________________________________________ >> Pulp-dev mailing list >> Pulp-dev@redhat.com >> https://www.redhat.com/mailman/listinfo/pulp-dev >> >
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev