| ... | ... | @@ -277,3 +277,26 @@ If these workarounds do not fit well with what you need and you absolutely want |
|
|
|
- Inria gitlab does not support custom domains and certificates. They are required if you want to have a custom domain that you own point to a gitlab pages generated site (optionnaly in https) but Inria has explicitely forbidden this functionnality.
|
|
|
|
- The first time Gitlab-Pages are activated, a question is asked: *"Authorize GitLab Pages to use your account? An application called GitLab Pages is requesting access to your GitLab account. Please note that this application is not provided by GitLab and you should verify its authenticity before allowing access. This application will be able to: Access the authenticated user's API, Grants complete read/write access to the API, including all groups and projects, the container registry, and the package registry."*. This is strange, but normal. The Gitlab-Pages server is a separate server, and for situation where pages are restricted to project members, the Gitlab-Pages server must use the authentication infrastructure of the Gitlab server. So you need to answer yes.
|
|
|
|
|
|
|
|
## Broken Links with Uploaded Files in a Project Wiki
|
|
|
|
|
|
|
|
The symptom is that when clicking on links to uploaded resources, an error 404 is thrown. The link follows the pattern `(/uploads/4d0b0eecbe6f0bd95a96f3b90cf64fe3/my_file.pdf)`.
|
|
|
|
In that case, check that the file `uploads/4d0b0eecbe6f0bd95a96f3b90cf64fe3/my_file.pdf` is not in the git repository of the wiki by:
|
|
|
|
1. cloning the wiki repository (button at the upper right of the wiki);
|
|
|
|
2. checking with `ls uploads/4d0b0eecbe6f0bd95a96f3b90cf64fe3/my_file.pdf` whether the file is stored in the repository. If it not, then you are in the situation addressed by this FAQ entry.
|
|
|
|
|
|
|
|
### Explanation
|
|
|
|
The way the linked files are stored in the wiki has changed (cf. https://docs.gitlab.com/ee/user/project/wiki/#attachment-storage): previously to gitlab 11.3 release, the linked files of all the wikis were uploaded in a global /uploads directory. Since 11.3, they are uploaded to a uploads directory pertaining to the git repository of the wiki.
|
|
|
|
|
|
|
|
But the files that were uploaded previously to 11.3 have not been moved to the wiki repositories, causing:
|
|
|
|
* 404 errors since it appears the global repository is not used anymore when gitlab follows the links inside the wiki;
|
|
|
|
* the files are not present when cloning the wiki repository, making the clone incomplete.
|
|
|
|
|
|
|
|
### Workarounds
|
|
|
|
|
|
|
|
If the file is not stored in the git repository of the wiki, two solutions exist:
|
|
|
|
#### Quick and Dirty Workaround
|
|
|
|
Change the `(/uploads/4d0b0eecbe6f0bd95a96f3b90cf64fe3/my_file.pdf)` links to `(https://gitlab.inria.fr/uploads/4d0b0eecbe6f0bd95a96f3b90cf64fe3/my_file.pdf)`.
|
|
|
|
#### Long-term Solution
|
|
|
|
It requires to download and the upload again each linked file:
|
|
|
|
* the file can be downloaded using the link given in the previous section;
|
|
|
|
* then upload the file using the "attach a file" button at the bottom right of the wiki editor. |
|
|
\ No newline at end of file |
