AIUI we have this support already, but we need to fix it up. The support comes from here: https://github.com/pulp/ansible-pulp/tree/master/roles/pulp-webserver#pulp-webserver
Currently though we need to fix both the apache and nginx configs to reverse proxy to 2 places if the first one 404s. first try the pulp API then the content app both on port 80. We have these stories as part of this epic here: https://pulp.plan.io/issues/4961 The apache one is here: https://pulp.plan.io/issues/4967 On Wed, Jul 10, 2019 at 8:31 AM Dennis Kliban <dkli...@redhat.com> wrote: > I am proposing that we provide additional support for deploying with httpd > as the reverse proxy. > > On Wed, Jul 10, 2019 at 8:27 AM David Davis <davidda...@redhat.com> wrote: > >> To clarify, are you proposing we should drop support for nginx in >> ansible-pulp in favor of apache? Or are you proposing we add support for >> httpd? I think the latter makes sense. >> >> David >> >> >> On Tue, Jul 9, 2019 at 9:06 PM Dennis Kliban <dkli...@redhat.com> wrote: >> >>> Our ansible role[0] for deploying Pulp 2 deploys httpd and has it bind >>> to ports 80 and 443. The ansible-pulp roles[1] deploy nginx and have it >>> bind to port 80 also. When Pulp 2 is already installed, nginx fails to >>> start. >>> >>> We need to add support to ansible-pulp for deploying Pulp 3 with httpd >>> instead of nginx. >>> >>> Does anyone have other solutions? >>> >>> >>> [0] https://github.com/pulp/pulp-ci/tree/master/ci/ansible/roles/pulp >>> [1] https://github.com/pulp/ansible-pulp >>> _______________________________________________ >>> Pulp-dev mailing list >>> Pulp-dev@redhat.com >>> https://www.redhat.com/mailman/listinfo/pulp-dev >>> >> _______________________________________________ > Pulp-dev mailing list > Pulp-dev@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-dev >
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev