Add the .gitlab-ci.yml and make it work with gitlab pages

[yodatak]

Hi i try to use liascript and gitlab ci to export the html to gitlab pages but i got many 404 and i want to know if you already use it for information here the config i use

I think it could be cool to make it works with gitlab ci and gitlab pages

https://gitlab.com/yodatak/liascript https://gitlab.com/yodatak/liascript/-/pipelines/420017444 https://yodatak.gitlab.io/liascript

It work directly from the artifact but not the gitlab pages https://yodatak.gitlab.io/-/liascript/-/jobs/1837074994/artifacts/export/index.html

I'm here to help this make its works ^^ Maybe its the index.*js that gitlab pages don't like

[SebastianZug]

Dear yodatak,

many thanks for your feedback. I'll take a look at the problem this weekend.

Sebastian

[SebastianZug]

Dear yodatak,

when I received your question, I took a view on the gitlab page of your project and received a 404. But when I am started to investigate the problem it works fine - Maybe we were just a little impatient :-)

I made some tests in a separate fork, the pipeline responses depending on the complexity of your course. For the last changes, I had to wait approximately 30 seconds for an update.

https://sebastian_zug.gitlab.io/liascript/?course.md#2

What are you going to implement with liascript? I am curious :-)

Best wishes Sebastian

[BeastyBlacksmith]

It found it works quite well with gitlab-pages, except for links to local resources, e.g. in this course I wanted to show a figure and had

![LMO1](plots/LMO1.png)

in the source file, but it is looking for that file relative to the root directory instead of relative to the project url.

Anything I can do about it?

[andre-dietrich]

@BeastyBlacksmith ... As you mentioned, LiaScript expects the README to be in the root-path and that sources are defined relative to it. However, if this is not the case, you can set a another base-path, similarly as it is done with HTML. This was mentioned here:

Issue 18