Pulp

++ This bug was initially created as a clone of Bugzilla Bug #1180753 ++

Description of problem:

Description of problem:
It is not possible to host Pulp at a different path than the default apache conf ships with, as many pieces of Pulp assume that Pulp will be hosted at a particular path and port. We should have a setting that lets Pulp know where it is hosted so that it can generate accurate hrefs when it is hosted in different locations.

Version-Release number of selected component (if applicable):
2.4.3-1

How reproducible:
Every time.

Steps to Reproduce:
1. Try to host Pulp on a different port, or at a different path, or both.

Actual results:
You will not be able to use Pulp when Apache is configured differently.

Expected results:
You should be able to run Pulp on any port or path you like. All components should continue to work.

--- Additional comment from bbouters@redhat.com at 01/12/2015 17:48:18 ---

Django has a place where you can set the 'deployed' URL, so that should read the Pulp setting. Then whenever code goes to build a 'full' URL, it should have Django form the full URL.

--- Additional comment from rbarlow@redhat.com at 01/12/2015 19:24:32 ---

(In reply to bbouters from comment #1)

Django has a place where you can set the 'deployed' URL, so that should read
the Pulp setting. Then whenever code goes to build a 'full' URL, it should
have Django form the full URL.

+1

--- Additional comment from mhrivnak@redhat.com at 01/14/2015 03:23:05 ---

Can you be more specific about what doesn't work when deployed to a non-standard port?

--- Additional comment from rbarlow@redhat.com at 01/14/2015 18:41:55 ---

I think the port element of this might not be true, so let's focus on the path part.