From a1f2af2f65d8dafb93b25effcb1aeef720eea614 Mon Sep 17 00:00:00 2001 From: curben Date: Wed, 17 Oct 2018 17:12:36 +1030 Subject: [PATCH] Update file links --- FAQ.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/FAQ.md b/FAQ.md index c0f7ce5..c5f6a0d 100644 --- a/FAQ.md +++ b/FAQ.md @@ -5,9 +5,11 @@ + It doesn't show the status (online/offline) of a URL. - Why don't you `wget top-1m.csv.zip` and output to stdout? - + If wget fails, [top-1m.txt](src/top-1m.txt) will be empty. Output as file avoids that. + + If wget fails, [top-1m.txt](https://gitlab.com/curben/urlhaus-filter/blob/master/src/top-1m.txt) will be empty. Output as file avoids that. - Why do you need to clone the repo again in your CI? I thought CI already fetch the repo by default? - + GitLab Runner clone/fetch the repo using HTTPS method by default ([log](https://gitlab.com/curben/urlhaus/-/jobs/105979394)). This method requires deploy *token* which is *read-only* (cannot push). + + GitLab Runner clone/fetch the repo using HTTPS method by default ([log](https://gitlab.com/curben/urlhaus-filter/-/jobs/105979394)). This method requires deploy *token* which is *read-only* (cannot push). + Deploy *key* has write access but cannot be used with the HTTPS method, hence, the workaround to clone using SSH. - + See issue [#20567](https://gitlab.com/gitlab-org/gitlab-ce/issues/20567) and [#20845](https://gitlab.com/gitlab-org/gitlab-ce/issues/20845). \ No newline at end of file + + Another approach is [personal access token](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html) which seems HTTPS-compatible. + + Deploy/SSH key is preferred because it can be [restricted](https://docs.gitlab.com/ce/ssh/README.html#per-repository-deploy-keys) to access one repo only, unlike personal access token which has [global](https://docs.gitlab.com/ce/ssh/README.html#global-shared-deploy-keys) access. + + See issue [#18106](https://gitlab.com/gitlab-org/gitlab-ce/issues/18106), [#20567](https://gitlab.com/gitlab-org/gitlab-ce/issues/20567) and [#20845](https://gitlab.com/gitlab-org/gitlab-ce/issues/20845). \ No newline at end of file