We're looking at developing apache/nginx scripts, and I was thinking about
documenting the webserver requirements. I think Pulp probably has to be
rooted at / on any given site so that it can host live APIs. Users can
still vhost multiple sites at other hostnames so I think it's ok, but I'm
On 11/02/2017 11:48 AM, Brian Bouterse wrote:
> Yes what you've written is the idea. An alternative implementation would be
> for the option field to be json
> field which postgres supports now, but either way works. Those 'options' are
> used during publishing as a
> mechanism to allow
Yes what you've written is the idea. An alternative implementation would be
for the option field to be json field which postgres supports now, but
either way works. Those 'options' are used during publishing as a mechanism
to allow arbitrary options to be passed to the the publisher, and later
I've been working on a planning task for how Pulp 3 will handle global
importer settings. As part of that, I've collected feedback from a number
of stakeholders. You can view the planning task here:
https://pulp.plan.io/issues/2373
The aspect that everyone seems to agree on is that proxies
