... | ... | @@ -192,9 +192,16 @@ Gitlab groups are the alternative to Forge projects hierarchy, and they are actu |
|
|
|
|
|
## Forge Web Hosting
|
|
|
|
|
|
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.
|
|
|
There are several INRIA alternatives to the forge web hosting, depending on the needs:
|
|
|
|
|
|
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.
|
|
|
* Wordpress hosting for INRIA Teams websites: https://team.inria.fr/
|
|
|
* Wordpress hosting for projects in general (research projects, collaborations, : https://project.inria.fr/
|
|
|
* Static files storage https://wiki.inria.fr/support/Espace_web is intended to store files used by a website. It is accessible with webdav, so it's possible to setup automated rsync to this place.
|
|
|
* Finally, Gitlab includes 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. 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.
|
|
|
|
|
|
One point worth noting is that contrary to previously, INRIA has decided that a team website has URL <team name>.inria.fr and nothing except teams can have such inria subdomains. Therefore, it has been decided that custom domains / certificates are disabled in gitlab-pages. It means that it is not possible to alias a DNS name to a gitlab-pages website.
|
|
|
|
|
|
It is also possible to move forge websites to non-INRIA hosting.
|
|
|
|
|
|
We are currently evaluating the possibility to offer the possibility to redirect the web hosting of forge projects to new URLs.
|
|
|
|
... | ... | |