You need to sign in or sign up before continuing.
Divide GitLab Pages settings into common and advanced
Sparked from the discussion !47749 (merged) and object storage work.
We add a lot of fine-tuning parameters to pages, which allow us to resolve issues on gitlab.com without need to recompile GitLab Pages.
These parameters are mostly useless for self-managed customers because we have very good defaults for them. (e.g. 90% of the time we use these defaults for gitlab.com ourselves). And changing these parameters can be harmful to the end users unless they know very well what they are doing(at the level when they can contribute to the pages codebase).
The idea is to divide parameters in our documentation into 2 sections:
- common params which change the behavior of pages service(e.g. enabling nginx proxy, SSL configuration...)
- fine-tuning params that don't change the behavior but can be useful under the high load. End users aren't advised to change these parameters.