This update took a bit longer than I expected

[You know these round tuits have been sitting on your desk for many years now, right? —Editor / I … um … erm … —Sean] [1]

I once mentioned updating mod_litbook [2] to run under a later version of Apache [3]. I wanted to do that because I've been running two instances of Apache—a later version that reverse proxies back to Apache 1.3 which just runs mod_litbook and nothing else, just to save me the agony of porting the code at the time. It only took me twelve years to locate the round tuit on my desk, but hey, better late than never.

I did do a mod_lua version of mod_litbook [4] first, based on the version running on my Gemini server [5]. With that (twelve years after I first played with mod_lua [6]) and two hours of time, I was able to match the output from the original version [7] (nice!). But it should be easy to update the actual mod_litbook source code to the latest version of Apache [8], right?

Right?

Yeah, kind of. it took two days, but I got it updated. I wasted the better part of a few hours trying to follow the instructions in the modules/examples directory which turns out to be laughably out of date. Once I found the proper guide [9] things went much more smoothly—mostly function name changes and removing calls to obsolete functions. I also decided to go ahead and use the Apache Portable Runtime [10] API (Application Programming Interface) instead of standard C functions as long as I was updating the code.

Now I just have to install the latest version of Apache on my server.

Just.

Yeah.

[1] /boston/2020/02/26/tuit.png

[2] /boston/2010/04/03.1

[3] https://httpd.apache.org/

[4] https://github.com/spc476/mod_litbook

[5] gemini://gemini.conman.org/

[6] /boston/2010/04/06.3

[7] http://bible.conman.org/kj/Revelation.1:8

[8] https://httpd.apache.org/docs/2.4/

[9] https://httpd.apache.org/docs/2.4/developer/modguide.html

[10] https://apr.apache.org/

Gemini Mention this post

Contact the author