Create documentation artifacts

I wasn't aware our current GitLab CI config did not publish the built documentation at all. This fixes this in a way that does not exhibit the problems I was facing last time where directing GitLab to work directly in the "result/" symlink dir (the nix store) would lead to all sorts of problems.

approved this merge request

added 1 commit

• eb278e3c - Expose documentation - experiment - single file

Compare with previous version

added 11 commits

• eb278e3c...5aa21a5f - 5 commits from branch develop
• f2fb9644 - CI Config: Publish built docs again
• dd5ce2dc - No variables like this in here
• c2af634e - TIL how to copy directories proper
• 0745581d - This could fix the paths to behave as expected
• ed28415d - the fewer code the better
• bd604dff - Expose documentation - experiment - single file

Compare with previous version

I rebased this on develop so the CI pipeline ran. Then I force-pushed.

What's your stance on this @jcalderone? Should I have merged develop into this branch instead?

added 1 commit

• 0fc58afa - docs artifact: expose directory instead

Compare with previous version

I was experimenting with expose_as before and did not see it's value. I would have liked to be able to browse the docs from GitLab directly, but the Gitlab documentation on expose_as have me confused what I should expose to make it so (the directory? seems to not do what I want. The index.html file? seems also to not do what I want. Both? Haven't tried.)

I get on with life I merge this and we can fine-tune later if should we enable gitlab pages.

merged

mentioned in commit 2f46a307

resolved all threads