Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
47f5dab6
Commit
47f5dab6
authored
Jul 09, 2018
by
Marcia Ramos
Committed by
Achilleas Pipinellis (🌴 July 10 - July 20 🌴)
Jul 09, 2018
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Docs: make it clear that you need a completely separate domain for Pages
parent
e8d7b283
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
doc/administration/pages/index.md
doc/administration/pages/index.md
+2
-2
No files found.
doc/administration/pages/index.md
View file @
47f5dab6
...
...
@@ -49,8 +49,8 @@ supporting custom domains a secondary IP is not needed.
Before proceeding with the Pages configuration, you will need to:
1.
Have a
separate domain under which the GitLab Pages will be served. In this
document we assume that to be
`example.io`
.
1.
Have a
n exclusive root domain for serving GitLab Pages. Note that you cannot
use a subdomain of your GitLab's instance domain
.
1.
Configure a
**wildcard DNS record**
.
1.
(Optional) Have a
**wildcard certificate**
for that domain if you decide to
serve Pages under HTTPS.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment