[Pulp-dev] pulplift with source installs for developers

Brian Bouterse bbouters at redhat.com
Fri Jan 4 21:53:51 UTC 2019

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.


On Fri, Jan 4, 2019 at 4:49 PM Dennis Kliban <dkliban at 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 at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20190104/bfa7ae0a/attachment.htm>

More information about the Pulp-dev mailing list