GitLab FI

Select the appropriate namespace and project name

The project name is deterministically mapped to the name of the page where the project appears. In general, a project in GitLab with a path
https://gitlab.fi.muni.cz/ namespace/ [subns/…/]project.git
will be available at the URL
https:// namespace.pages.fi.muni.cz/ [subns/…/]project

Namespace user projects has namespace identical to the faculty login, a subns/…/ is empty because the user namespace does not have subgroups. Therefore, for sites related to the project of a subject or research group, we recommend using the group namespace.

Tip: I want to request the creation of a group

Web content

The structure of the pages, the language used, etc. depends on the selected generator, ie the program that creates the resulting static website. Most support it Markdown or AsciiDoc , however, you can also find specific generators, eg for generating documentation from source code. You can also write your own generator.

Get inspired by examples

look at official demonstrations repositories. Most of them can be used as a framework for your own project.

Pay attention to configuration files, it is often necessary to modify more than one configuration in templates. If the template has README.md or similar help, read it carefully.

Tests the configuration

We recommend that you start with a very small number of pages first to see if the generator works at all.

Custom generator

You can also use your own generator to generate content. Generation takes place like any other task for GitLab CI. For task setup requirements and where the result is expected, see official documentation .

CI / CD settings

You can use it to generate a site faculty instance of GitLab Runner or custom instance.

Don't forget to use the faculty instance

• set a tag for tasks shared-fi in .gitlab-ci.yml ,
• verify that the container image for your chosen generator is available for faculty GitLab CI, eg in application of faculty administration .