Actions
Task #3114
closedDocument the webserver requirements
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
Yes
Tags:
Documentation
Sprint:
Quarter:
Description
I think the docs would benefit from a small section added to them to documenting Pulp's webserver expectations. I believe all that is required is that it's a WSGI process and that it own the entire namespace.
This means that Pulp cannot be run side by side another application. They could use SNI to configure multiple vhosts on one server though so it's still about to run multiple sites, just not on one domain. The reason this would be required is that content types that require live APIs, e.g. crane, puppet forge, etc, they can have hard-coded urls. Only if all urls are passed and matched by Django can Pulp fulfil this use case.
Related issues
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 bmbouter almost 7 years ago
- Related to deleted (Task #2922: Create and publish an ansible role to install and configure nginx for pulp)
Updated by bmbouter almost 7 years ago
- Related to deleted (Task #2921: Create and publish an ansible role to install apache and configure it for pulp)
Updated by bmbouter almost 7 years ago
- Status changed from NEW to CLOSED - DUPLICATE
Updated by bmbouter almost 7 years ago
- Is duplicate of Task #3132: Document how to deploy Pulp added
Actions