From bcadf897da62964c8448add086bc03d6352109f8 Mon Sep 17 00:00:00 2001 From: Tuomo Ala-Vannesluoma Date: Tue, 3 Jul 2018 21:23:41 +0300 Subject: Update readme --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index 8ae6b0e4..fc0fc2bc 100644 --- a/README.md +++ b/README.md @@ -172,9 +172,9 @@ $ ./gitlab-pages -listen-http "10.0.0.1:8080" -listen-https "[fd00::1]:8080" -pa #### How it works -1. GitLab pages looks for `access_control`, `private` and `id` fields in `config.json` files +1. GitLab pages looks for `access_control` and `id` fields in `config.json` files in `pages-root/group/project` directories. -2. For projects that have `access_control` and `private` set to `true` pages will require user to authenticate. +2. For projects that have `access_control` set to `true` pages will require user to authenticate. 3. When user accesses a project that requires authentication, user will be redirected to GitLab to log in and grant access for GitLab pages. 4. When user grant's access to GitLab pages, pages will use the OAuth2 `code` to get an access -- cgit v1.2.3