Document how to deploy Pulp
Users should have docs on how they can configure the webserver to serve Pulp. This should be a "Webserver" section on a new page to be created in the docs called "Deploying".
These docs should explain to 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
/content/ and route that to the Pulp WSGI app. For the REST API part it needs to match on both
This documentation should not give examples for specific webservers. It should generally fulfill the following requirements:
As a deployer of Pulp, I understand the urls Pulp needs to serve the "Content" part of Pulp and that I need to route them to the Pulp WSGI app
As a deployer of Pulp, I understand the urls Pulp needs to serve the REST API and that I need to route them to the Pulp WSGI app
#3 Updated by bmbouter over 2 years ago
A question came up asking if this was making two new django apps. I had not planned on splitting the Django apps because practically speaking it would be hard to do so. Without actually making the content app a separate Django app, we aren't creating any value by having the same Django app served in another WSGI file with a different name.
Practically speaking, we don't need to ship multiple Django apps for the Pulp3 MVP, so I recommend this be closed as NOTABUG.
Please register to edit this issue