Commit 8aba28e1 authored by Achilleas Pipinellis's avatar Achilleas Pipinellis Committed by James Edwards-Jones

Clarify some things in Pages [ci skip]

* Pages are enabled by default on each project
* Add note about using the `only` parameter
parent 0bb480dc
...@@ -17,13 +17,14 @@ The steps that are performed from the initialization of a project to the ...@@ -17,13 +17,14 @@ The steps that are performed from the initialization of a project to the
creation of the static content, can be summed up to: creation of the static content, can be summed up to:
1. Create project (its name could be specific according to the case) 1. Create project (its name could be specific according to the case)
1. Enable the GitLab Pages feature under the project's settings
1. Provide a specific job in `.gitlab-ci.yml` 1. Provide a specific job in `.gitlab-ci.yml`
1. GitLab Runner builds the project 1. GitLab Runner builds the project
1. GitLab CI uploads the artifacts 1. GitLab CI uploads the artifacts
1. Nginx serves the content 1. Nginx serves the content
As a user, you should normally be concerned only with the first three items. As a user, you should normally be concerned only with the first three items.
If [shared runners](../ci/runners/README.md) are enabled by your GitLab
administrator, you should be able to use them instead of bringing your own.
In general there are four kinds of pages one might create. This is better In general there are four kinds of pages one might create. This is better
explained with an example so let's make some assumptions. explained with an example so let's make some assumptions.
...@@ -68,6 +69,13 @@ To make use of GitLab Pages, your `.gitlab-ci.yml` must follow the rules below: ...@@ -68,6 +69,13 @@ To make use of GitLab Pages, your `.gitlab-ci.yml` must follow the rules below:
1. Any static content must be placed under a `public/` directory 1. Any static content must be placed under a `public/` directory
1. `artifacts` with a path to the `public/` directory must be defined 1. `artifacts` with a path to the `public/` directory must be defined
Be aware that Pages are by default branch/tag agnostic and their deployment
relies solely on what you specify in `gitlab-ci.yml`. If you don't limit the
`pages` job with the [`only` parameter](../ci/yaml/README.md#only-and-except),
whenever a new commit is pushed to whatever branch or tag, the Pages will be
overwritten. In the examples below, we limit the Pages to be deployed whenever
a commit is pushed only on the `master` branch, which is advisable to do so.
The pages are created after the build completes successfully and the artifacts The pages are created after the build completes successfully and the artifacts
for the `pages` job are uploaded to GitLab. for the `pages` job are uploaded to GitLab.
...@@ -84,6 +92,8 @@ pages: ...@@ -84,6 +92,8 @@ pages:
artifacts: artifacts:
paths: paths:
- public - public
only:
- master
``` ```
## Example projects ## Example projects
...@@ -101,10 +111,9 @@ in the artifacts. ...@@ -101,10 +111,9 @@ in the artifacts.
## Frequently Asked Questions ## Frequently Asked Questions
**Q:** Can I download my generated pages? **Q: Can I download my generated pages?**
**A:** Sure. All you need to do is download the artifacts archive from the Sure. All you need to do is download the artifacts archive from the build page.
build page.
--- ---
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment