[Pulp-dev] Webserver owning the entire url namespace?

Brian Bouterse bbouters at redhat.com
Mon Nov 6 17:36:21 UTC 2017

Yes Pulp should operate under some path, and it does. The issue that some
of the "live APIs" just can't be (docker, puppet, etc) because they have
hard-coded url expectations. Those live APIs will be served via a viewset
in core Pulp. So while Pulp can be rerooted, it can't serve some live APIs
depending on how that rerooting is done.

So to allow as many live APIs as possible, the default Pulp deployment
would be one that is rooted at /  Users can root Pulp other ways, but their
live APIs may break. The core docs would just say that. In terms of how to
deploy Pulp in a rooted way and still have the live APIs work, plugin
writers and users would figure that out those configurations directly.

In cases where a plugin writer doesn't distribute their live API code as a
separate package outside of Pulp, there isn't something the user, or Pulp
core could do, to make a re-rooted Pulp install serving that live API work.

Thoughts, questions, alternatives, ideas?

On Mon, Nov 6, 2017 at 9:43 AM, Jeremy Audet <jaudet at redhat.com> wrote:

> +1 to requiring that Pulp be able to operate underneath some path.
> Well-behaved web application should support this. It's a common
> expectation, and we should live up to common expectations.
> For a real world example of how to make an application behave well
> underneath a base path, see Syncthing's Reverse Proxy Setup
> <https://docs.syncthing.net/users/reverseproxy.html> documentation.
> _______________________________________________
> 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/20171106/710cc278/attachment.htm>

More information about the Pulp-dev mailing list