[Pulp-list] A different way to setup Pulp for development

[James Slagle]

On Wed, Jun 27, 2012 at 10:11:07AM +1000, Nick Coghlan wrote:
> On 06/27/2012 01:37 AM, James Slagle wrote:
> > Any feedback is appreciated. So far I've logged in and created and sync'd a
> > repo.  Enough to show I basically had it working, but I'm sure there might be
> > some issues. 
> > 
> > I'm not looking to merge this into master anytime too soon (master was just
> > merged into my branch this morning, fyi).  It's more of a POC to see if it was
> > possible.  But, I think this is a valuable effort, and would make getting setup
> > to do Pulp development easier.  We in fact have someone else in the community
> > who was essentially trying to do the same thing as well.
> 
> Being able to test under a non-root Apache would be great. It would be
> handy if there was a helper script or module to appropriately symlink in
> custom plugins, though.

Yes, running as non-root was definitely one of my side goals in addition to
having multiple versions running simultaneously.

As far as a script to link plugins, what did you have in mind?  Do you mean
plugins that are already installed on your system in the normal locations, just
a way to symlink those to the correct place under the new top level directory?
Or, plugins that you were actively developing?  I'm not sure how we'd know
where to look for those, although we could introduce an environment variable
set to their location.

--
-- James Slagle
--