| [ << Website work ] | [Top][Contents] | [ LSR work >> ] |
| [ < Introduction to website work ] | [ Up : Website work ] | [ Debugging website and docs locally > ] |
6.2 Uploading website
Overall idea
The website is generated by converting the ‘Documentation/*/web.texi’ files to HTML, and reorganizing the resulting files into ‘out/website-root/’. This is controlled from toplevel ‘GNUmakefile’ and ‘Documentation/GNUmakefile’.
To build the website, run make website. This leaves the
website in ‘out/website-root/’.
The website is deployed onto lilypond.org in the following
steps:
- Run the manual job to build the website, either for the merge
request you want to deploy or for the latest pipeline on
masterat https://gitlab.com/lilypond/lilypond/-/pipelines, by clicking the play button. - This runs
make websiteand stores the result in a ‘website.zip’ artifact. - On
lilypond.org, the downloader https://gitlab.com/lilypond/infrastructure/-/blob/master/website/main.go is run every 2 hours, from a systemd timed job. If a newer ‘website.zip’ is found, it is unpacked into the ‘website’ directory onlilypond.org.
| [ << Website work ] | [Top][Contents] | [ LSR work >> ] |
| [ < Introduction to website work ] | [ Up : Website work ] | [ Debugging website and docs locally > ] |