schallbert/lectures
1
0
Fork 0
Code Pull Requests Actions Activity

Compare commits

base: schallbert:a31e8268eaf8062d0c1811012efc9d8af340503c
Branches Tags
schallbert:main
schallbert:maintenance
schallbert:deploy-fix
schallbert:personalauswahlalgorithmen
schallbert:styling-update
schallbert:landing-style-update
..
compare: schallbert:69093b5d0bb1054bafed4dc30d7fa39ade6a080e
Branches Tags
schallbert:main
schallbert:maintenance
schallbert:deploy-fix
schallbert:personalauswahlalgorithmen
schallbert:styling-update
schallbert:landing-style-update

No commits in common. "a31e8268eaf8062d0c1811012efc9d8af340503c" and "69093b5d0bb1054bafed4dc30d7fa39ade6a080e" have entirely different histories.
a31e8268ea ... 69093b5d0b

1 changed files with 1 additions and 3 deletions
Show Stats Expand all files Collapse all files

2
README.md
View File

@ -6,5 +6,3 @@ The website displaying this content can be reached under [https://lectures.schal
### Mechanics behind ### Mechanics behind
I use the `react.js` framework so my lectures can be displayed neatly in any browser. From this repository, the sources are checked out by an automation from Gitea called *act_runner* that listens to repository push. It then deploys the `html` output to my webserver solution *caddy* so the content can be displayed on any client's browser. I use the `react.js` framework so my lectures can be displayed neatly in any browser. From this repository, the sources are checked out by an automation from Gitea called *act_runner* that listens to repository push. It then deploys the `html` output to my webserver solution *caddy* so the content can be displayed on any client's browser.
As the *act_runner* will use `main`, I disallowed pushing to it.