... | ... | @@ -270,6 +270,8 @@ It is intended to store static files or web sites served with https. It is acces |
|
|
|
|
|
URLs are in the form ```https://files.inria.fr/<sitename>```. It supports virtual hosting, meaning that it can be configured to serve page for an alternate URL, in the inria domain (for example ```https://<project>.inria.fr``` or not (for example ```https://<project>.org```). For non inria domains, you need to rent the domain name.
|
|
|
|
|
|
To request a space on files.inria.fr, submit a ticket. Provide the name of the space you want, and the ildap logins of the people who should be able to have write access. To update this space, any webdav client can be used. For example, on linux + gnome you can access the space in the file manager with a location such as ```davs://<ildap user name>@files.inria.fr:8443/<space name>```. You can also mount this space in the file system with tools such as davfs2 or gvfs-fuse. For example, on debian linux + gnome, install package gvfs-fuse, and when the space is "mounted" in the gnome file manager, it will also be mounted in the filesystem at location ```/run/user/<local unix user numeric id>/gvfs/dav:host=files.inria.fr,port=8443,ssl=true,user=<ildap login>/<space name>/```. You can then rsync your forge site to the files.inria.fr site with a command such as: ```rsync --delete --exclude=.htupdate -rl <forge username>@forge-scm2:/home/groups/<forge unix project name>/htdocs/ /run/user/<local unix user numeric id>/gvfs/dav:host=files.inria.fr,port=8443,ssl=true,user=<ildap login>/<space name>/```. If using option ```--delete``` make sure to not delete ```.htupdate``` since it controls who has write access. Also do not use ```-a```, it doesn't work with webdav, use ```-rl``` instead.
|
|
|
|
|
|
## gitlabpages
|
|
|
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.
|
|
|
There is an example project showing how to setup gitlabpages here: https://gitlab.inria.fr/siteadmin/pages-example
|
... | ... | |