admin2/manual_teachbooks
1
0
Fork 0
mirror of https://github.com/TeachBooks/manual.git synced 2026-11-13 23:05:51 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Moved stuff from install chapter and restructured

Browse source
This commit is contained in:
Tom van Woudenberg 2024-03-25 09:56:38 +01:00
parent 9b7034d4cd
commit 05f7e7e86a
12 changed files with 200 additions and 122 deletions
Download patch file Download diff file Expand all files Collapse all files

15
book/features/buildbook.md Normal file
View file

@ -0,0 +1,15 @@
# Book build on webserver / GitHub Pages
Now that we have talked about how you can collaborate using git, it's time to explain how the book is actually built.
## GitLab Pages
## GitHub Pages
## Pipeline
Both GitLab and GitHub make use of CI/CD to publish the jupyter books. CI/CD stands for Continuous Integration/Continuous Deployment. Within the scope of jupyter books focuses on automating the process of building and deploying the books. It makes sure that the book is always up-to-date and available.
Concretely, Continuous Integration means that whenever changes are pushed to the repository (where does the publish branch come in?) the pipeline is triggered. Moreover, the pipeline also builds the book which is composed out of multiple .md or .ipynb files and converts those files into HTML.
Continuous Deployment ensures that the book is deployed onto the desired destination (in our case the website) and accessible to the readers.