Nice job! I have been doing something with practically the same purpose. Look:
The .gitlab-ci.yml is:
image: texlive/texlive
before_script:
- export DEBIAN_FRONTEND=noninteractive
- apt-get -y update && apt-get -y upgrade
- apt-get -y install curl hunspell hunspell-es linkchecker neofetch pandoc ruby uuid-runtime
- gem install bibtex-ruby httparty nokogiri
- mkdir kindlegen && cd kindlegen && wget https://archive.org/download/kindlegen_linux_2.6_i386_v2_9.tar/kindlegen_linux_2.6_i386_v2_9.tar.gz && tar -xvzf kindlegen_linux_2.6_i386_v2_9.tar.gz && mv kindlegen /usr/local/bin/ && cd .. && rm -rf kindlegen
# Tools for specific purposes, you can ignore them
- wget https://gitlab.com/snippets/1917492/raw -O /usr/local/bin/baby-biber && chmod +755 /usr/local/bin/baby-biber
- wget https://gitlab.com/snippets/1917490/raw -O /usr/local/bin/export-pdf && chmod +755 /usr/local/bin/export-pdf
- wget https://gitlab.com/snippets/1917487/raw -O /usr/local/bin/texti && chmod +755 /usr/local/bin/texti
# We prefer to do the ebook with this legacy tool for compatibility purposes
- (cd ~ && mkdir .pecas && cd .pecas && git clone --depth 1 https://gitlab.com/programando-libreros/herramientas/pecas-legacy.git . && bash install.sh) && source ~/.profile
pages:
stage: deploy
script:
- mkdir public/
# Test 1: gather info about the software and hardware
- cp index.html public/ && cd public/
- printf "\n# neofetch\n" >> log.txt
- neofetch | sed 's/\x1B\[[0-9;\?]*[a-zA-Z]//g' >> log.txt
- printf "\n# uname -a\n" >> log.txt
- uname -a >> log.txt
- printf "\n# apt list --installed\n" >> log.txt
- apt list --installed >> log.txt
- printf "\n# ls /sbin\n" >> log.txt
- ls /sbin >> log.txt
- printf "\n# ls /bin\n" >> log.txt
- ls /bin >> log.txt
- printf "\n# ls /usr/bin\n" >> log.txt
- ls /usr/bin >> log.txt
- printf "\n# ls /usr/local/bin\n" >> log.txt
- ls /usr/local/bin >> log.txt
- printf "\n# tlmgr list --only-installed\n" >> log.txt
- tlmgr list --only-installed >> log.txt
- printf "\n# ruby --version\n" >> log.txt
- ruby --version >> log.txt
- printf "\n# gem list\n" >> log.txt
- gem list >> log.txt
- printf "\n# kindlegen\n" >> log.txt
- kindlegen >> log.txt
- printf "\n# texti\n" >> log.txt
- texti >> log.txt
- printf "\n# pc-doctor\n" >> log.txt
- pc-doctor >> log.txt
# Test 2: publish an existent repo
- git clone --depth 1 https://gitlab.com/NikaZhenya/maestria-investigacion.git && cd maestria-investigacion/tesis && ./generate-all && cd ..
- rm -rf .g* administrativo apuntes bibliografia protocolo && cd ..
# Test 3: publish a HedgeDoc pad! (actually anything that has raw MD)
- mkdir pad && cd pad && wget https://pad.programando.li/Pgs01Hr3QgWtgspU6YbhkA/download -O pad.md
- pandoc pad.md -s -o index.html
- pandoc pad.md -o pad.pdf
- pandoc pad.md -o pad.epub
- pandoc pad.md -o pad.docx
#- kindlegen pad.epub # It works, but if it ends with warnings, the job fails
artifacts:
paths:
- public
only:
- master
As yo can see, I decided to use the texlive/texlive container because our needs implies a heavy use of latex. I still haven’t add pandoc-citeproc, but it is because we are gonna deploy a container based on texlive container. I think like 40% of the time could be saved if we already have a container with all the needed tools (we are gonna probably add other publishing systems that use MD like jekyll, pelican and hugo)
Another thing to do that I am gonna work this weekend is enable a variable so it can be use with any MD url, like hedgedoc links.
The Test 2 could be of your interest, it is a complete research thesis (spanish) with a site and so on.
Cheers, nice to see ppl working on the same things!
The second publishing revolution has just began 
