Skip to content

Docs: Polish "Pages on separate server" setup

What does this MR do?

Closes gitlab-com/support/support-team-meta#2469 (closed).

Based on , @nelbacha and me think they are currently not complete(ly correct). In order to streamline the setup of GitLab pages on an external / separate server, should the documented steps be clarified?

This MR removes 2 error sources and suggests to:

a) group the GitLab server and Pages server steps a bit more logically,

b) note the differences of the Pages setup compared to the broader example in the NFS docs, and

c) to include a pages-specific test of the NFS share.

d) Additionally, placeholder variables are made to conform to the style guide.

Related issues

Author's checklist (required)

Do not add the feature, frontend, backend, ~"bug", or database labels if you are only updating documentation. These labels will cause the MR to be added to code verification QA issues.

When applicable:

Review checklist

All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.

1. Primary Reviewer

  • Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.

2. Technical Writer

  • Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.

3. Maintainer

  1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
  2. Ensure a release milestone is set.
  3. If there has not been a technical writer review, create an issue for one using the Doc Review template.
Edited by Katrin Leinweber

Merge request reports