Task #3132
closed
Document how to deploy Pulp
100%
Description
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 /api/v3/.
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
Related issues
Updated by dalley about 7 years ago
- Tracker changed from Issue to Task
- % Done set to 0
Updated by bmbouter about 7 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.
Updated by bmbouter about 7 years ago
- Subject changed from Create and document WSGI applications to Document how to deploy Pulp
- Description updated (diff)
- Tags Documentation added
Rewriting after IRC convo where the goal became to convert this to a docs story and document the Pulp requirements.
Updated by bmbouter about 7 years ago
- Has duplicate Task #3114: Document the webserver requirements added
Updated by bmbouter about 7 years ago
- Related to Task #2922: Create and publish an ansible role to install and configure nginx for pulp added
Updated by bmbouter about 7 years ago
- Related to Task #2921: Create and publish an ansible role to install apache and configure it for pulp added
Updated by jortel@redhat.com almost 7 years ago
- Sprint/Milestone changed from 53 to 54
Updated by jortel@redhat.com almost 7 years ago
- Sprint changed from Sprint 33 to Sprint 34
Updated by bmbouter almost 7 years ago
- Description updated (diff)
Removing /status/ from description because it is actually nested under /api/v3/
Updated by daviddavis over 6 years ago
- Sprint changed from Sprint 34 to Sprint 35
Updated by bmbouter over 6 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to bmbouter
Updated by bmbouter over 6 years ago
- Status changed from ASSIGNED to POST
PR available at: https://github.com/pulp/pulp/pull/3429
Added by bmbouter over 6 years ago
Added by bmbouter over 6 years ago
Revision 29e34cab | View on GitHub
Adds WSGI and Architecture Docs
This creates an Architecture and Scaling top level section of the docs. It also explains for each component how it can be scaled which mostly involves documenting how the WSGI application is laid out.
Updated by bmbouter over 6 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp|29e34cabfa0f63f1891b4a69151998fef30fae78.
Updated by bmbouter about 5 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
.
Adds WSGI and Architecture Docs
This creates an Architecture and Scaling top level section of the docs. It also explains for each component how it can be scaled which mostly involves documenting how the WSGI application is laid out.
https://pulp.plan.io/issues/3132 closes #3132