| ... | ... | @@ -291,7 +291,7 @@ If these workarounds do not fit well with what you need and you absolutely want |
|
|
|
## Gitlab-Pages
|
|
|
|
|
|
|
|
- Gitlab-Pages are activated on our gitlab instance. Documentation can be found here: https://gitlab.inria.fr/help/user/project/pages/index.md
|
|
|
|
- Gitlab pages allow only static html content to be published (it means: no database, no php, etc.). The pages are generated as part of a continuous integration step, so you need a gitlab runner for the pages generation. As there is currently (April 2020) no shared runner on our instance, a workaround is to ask the support team, you'll be added to a special project which allows you to use a (beta testing) docker runner to build your pages instead of having to build and manage one yourself.
|
|
|
|
- Gitlab pages allow only static html content to be published (it means: no database, no php, etc.). The pages are generated as part of a continuous integration step, so you need a gitlab runner for the pages generation. You can use the shared runners available for this, see [existing shared runners](https://gitlab.inria.fr/siteadmin/doc/-/wikis/faq#use-existing-shared-runners).
|
|
|
|
- There is a basic gitlab-pages example project here: https://gitlab.inria.fr/siteadmin/pages-example The generated web page is here: https://siteadmin.gitlabpages.inria.fr/pages-example/
|
|
|
|
- You can also have a look at https://gitlab.inria.fr/help/user/project/pages/getting_started/new_or_existing_website.md note that there are templates for many website generators.
|
|
|
|
- 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.
|
| ... | ... | |
