Simplify GitLab Pages documentation
The GitLab Pages documentation at http://doc.gitlab.com/ee/pages/administration.html is valid - no doubt. But I wonder if it's too complicated for many of the customer/user installations out there. If I understand correctly, the reason for having multiple IPs and a separate domain are for security. Is there a compelling reason that smaller customers should n't run Pages on the same IP and use the built-in Nginx as a proxy? I understand this means SSL won't work, but maybe they don't care.
If we assume a simple case like this, then all the customer needs to do is set pages_external_url
in gitlab.rb
, set DNS, and everything should work.
Even in cases where SSL is required, I don't see a reason for us to 'force' users to use a secondary IP. What's wrong with turning off pages_nginx
and then the customer uses Nginx or another load balancer to proxy TCP on ports 80/443 so SSL works? Customers on an internal network aren't concerned about DDOS.
cc/ @ayufan @axil I look forward to your input. Throwing around ideas here.