Document single-IP solution for GitLab Pages
I use a web host that is limiting the number of IP addresses it hands out to its users. Thus, I would like to be able to run GitLab Pages on the same server as my GitLab instance by using the same IP.
Here is what the documentation currently says.
Run the pages daemon in the same server as GitLab, listening on the same IP but on different ports. In that case, you will have to proxy the traffic with a loadbalancer. If you choose that route note that you should use TCP load balancing for HTTPS. If you use TLS-termination (HTTPS-load balancing) the pages will not be able to be served with user provided certificates. For HTTP it's OK to use HTTP or TCP load balancing.
It would be nice if there was another document laying out how to do this. I would imagine that this will be the default implementation method for many users.
Activity
@iheart2code I've moved this issue to the Enterprise Edition tracker as the pages feature is only available in this product.
added ~155960 ~111707 pages labels
mentioned in issue #461 (closed)
changed milestone to %8.17
assigned to @axil
This is kinda infrastructure specific, but I guess we could provide some options on Nginx, and HAproxy which we use at .com. Related to https://gitlab.com/gitlab-org/gitlab-ee/issues/461.
mentioned in issue gitlab-com/gitlab-docs#69 (closed)