Task #3132

Updated by bmbouter about 2 years ago

Users should have docs on how they can configure the webserver to serve Pulp. The "current WSGI application": serves all URLs. This should be a "Webserver" section on a new page to be created in means we can't efficiently deploy/scale the docs called "Deploying".

These docs
API separately from the content serving webapplication. We should explain to split up the user the top level url(s) hat need to be matched for the "content" part of Pulp and the "REST API". Specifically the "content" part needs to match on <code>/content/</code> and route that to the Pulp current WSGI app. For the REST API part it needs to match on both <code>/api/v3/</code> application into two smaller WSGI apps and <code>/status/</code>. document them.

This documentation should not give examples for specific webservers. It should generally fulfill the following requirements:

Create an api.wsgi which will serve /status/ and /api/v3/ urls. Also create a deployer content.wsgi which serves /content/. Both of Pulp, I understand the urls Pulp needs to serve the "Content" part of Pulp and that I these need to route them to be documented on a new page in the Pulp WSGI app

There was
a deployer of Pulp, I understand long related thread on pulp-dev called "Webserver owning the urls Pulp needs to serve entire url namespace?": The last note "here": uses the REST API and that I need to route them to the Pulp WSGI app same language as this ticket.