guus/blog
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update git output section

Browse Source
This commit is contained in:
Guus Waals
2025-10-29 19:31:01 +08:00
parent 6096ebc43c
commit a88222184f
3 changed files with 35 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

27
posts/blog-server.md
View File

@@ -17,6 +17,33 @@ I wanted to have a setup that generates static html from something like markdown
I decided to do something similar, however I used rust as it has some popular existing libraries for web servers and parsing markdown. The reason for writing an application to host the blog is that I wanted to have it automatically respond to a git webhook which would automatically pull the latest git repo and then rebuild the articles from their markdown files.
## Parsing the git output
As mentioned in [this article](https://gaultier.github.io/blog/making_my_static_blog_generator_11_times_faster.html) they use the git log command to retrieve the blog files, which I decided to also use. I found out there is a way to retreive the output from git in the following predictable format:
```
c584d39 - 1761735775 - Update server post and fix post titles
:100644 100644 d5e614a 678eb09 M posts/blog-server.md
9d5f86a - 1761415068 - Template
:000000 100644 0000000 d5e614a A posts/blog-server.md
```
Retrieved with the following command line: `git log --raw --no-merges --pretty="%h - %ad - %s" --date=unix -- posts`
Where the first entry will always be a commit hash followed by unix time stamp and then the commit name. After that it will list files affected by this commit, prefixed with a colon (:).
Then we can simply parse this by reading line by line and attributing the following file changes to the commit that was above it. Then I use the first encounter of a given file to determine the creation date, and the last encounter to determine the update date.
### (Bonus) Parsing the git version
There's a nice trick to retrieve the current git branch and commit hash by just reading 2 files, which I grabbed from one of my CMake scripts that uses it to inject the git version into my code on every compile. It's super fast since it doesn't actually run any git commands to retrieve this information.
The process is, read .git/HEAD, which will either contain just the hash, or something like `ref: refs/heads/main`.\
In the later case, you can just read from .git/refs/heads/main which will then contain your git hash.
This version is inserted at the bottom of the page so I can tell which version it's at.
## HTML
Of course there is also some styling and markup required for the shell, like the navigation bar and footers.\