| ... | ... | @@ -84,6 +84,8 @@ Gitlab groups are the alternative to Forge projects hierarchy, and they are actu |
|
|
|
|
|
|
|
Web hosting in gitlab is done with gitlab pages. Gitlab pages can only serve static content, so this means no PHP (unlike the forge) or database. For example it is not possible to host a dokuwiki (which is php based). The generation of the pages is done with the same mechanisms as gitlab continuous integration. Any static site generator can be used (and there are templates for many). Gitlab pages are served over HTTPS but it has been decided that custom domains / certificates won't be activated.
|
|
|
|
|
|
|
|
A [gitlab runner](https://docs.gitlab.com/runner/) is needed to build gitlab pages. A gitlab runner is a server/VM/docker container running an agent and which can act as an executor for gitlab continuous integration jobs (and gitlab pages are a special case of gitlab continuous integration). As it is annoying for every project to setup a runner just for being able to publish a website, there is a work in progress to add shared runners to the inria gitlab. In the meantime, all projects requiring a runner for quick tasks like gitlab pages generation can ask to join the [qlf-ci-gitlab-runner](https://gitlab.inria.fr/inria-ci/qlf-ci-gitlab-runner) which provides such pseudo-shared docker runners.
|
|
|
|
|
|
|
|
## Forge Shell Access
|
|
|
|
|
|
|
|
Not available in gitlab
|
| ... | ... | |
