Ongoing

Seven primary areas (floating 8th for Sysadmin activities)...

API to (Headless) CMS (See next two)
Map Three-Phase Refactor (Caravan-Arbirated Orchestration)
Wiki Scaffolding (Thin proxy extension experiments)
Manifest Pipeline (Private pipe 100% done - examining PluggableAuth & OpenID Connect Extensions)
JobRunner overhaul (Blazorizing)
KenshiDB overhaul (Blazorizing)
C# Bridge (TestHarness talking... - Ghidra...)

11/11

The detour and investigation were a success, with caveats. The prognosis is terminal (sad) and the prospects for revision are untenable. Such as it is, the theoretical needle is going to require SigScanning - RVA matching is too brittle and caused the precise problems seen in attempted modernization. A salute to good work and a noble attempt. Moving along.

11/12

Plant trees you'll never sit in the shade of.

Energy harvest.

11/13

Placing the final touches on manifest management... Laying the groundwork for the overhaul of the wiki's UI-API relationship to the map, content management for KenshiDB (remember?) and "upgraded" job runner dashboard (this combined with refining the runner itself). The converging pipelines, dashboards & monitors invariably lead to returning to the map in earnest. Toying around in Ghidra, btw.

11/14

Snow day every day!

11/16

Quick on this one because there's a lot of good going on.

The (direct) manifest pipeline - local extraction & bundling, upload, unpacking & serving to the map is complete.
Establishing a thin proxy to serve the v1 (existing), v2 (in progress) and v3 (optimized) versions of the map's data underway.
Map orchestration is, aside from Caravan's role, largely to be managed through the observation point & smart switch on the backend for delivering the respective versions, if available (v1 always is).
The Job Runner & KenshiDB reworks (one more elaborate than the other) are in the outlining phase.
With the so-called direct access manifest pipeline up and running the map's feature development is back in fashion. The set is known - taking time to align them with the emerging new options setting & confirmation process. Caravan retains controls of configuration routines... easier to decouple that way.

An ocean of opportunities

11/17

I want you to watch the screen... There's something I want you to see... Have you... ever seen a portal...?

11/18

Antigravity (Google's Windsurf) just released. Check it out!

Patience prevails.

Kenshi Wiki's full tech stack

A brief overview of the languages and approaches to the site's composition, subject to some change...

Hosted on Ubuntu 24.04 (this may change!)

Web server...

Nginx, Varnish & Cloudflare for DNS

MariaDB for MySQL

Most logging (and the Job Runner) are managed through Cron jobs (Bash).

Sites...

HTML, CSS & Javascript - standard, friendly, used everywhere, unavoidable.

The wikisite is primarily focused on PHP on the backend, mostly Javascript and Lua focused on the frontend

The interactive map uses a basic setup of HTML, CSS & Javacript, for now.

This is subject to change, Typescript integration is underway - DB migration thereafter.

The other sites, Manifestor, File Storage (KenshiDB) & Wiki Job Runner are managed through Blazor.

C#, Razor, Entity Framework, ASPNET, OAuth...systemd.

Experimenting with Go, F# (Bolero) and Cloudflare Workers.

Note on this - no integration intentions as of yet, simply experimenting. Except CFWs - those are desirable later optimizations.

External tools: Both the KenshiDataTools (Extraction + Manifestation) & the Kenshi SDK (KenshiConnector and its growing list of submodules) are written in C#.; I tend to do most development in Visual Studio / + (Code) nowadays. VSC is especially nice with its SSH add-on - reason enough to acquiesce to the .NET ecosystem.
Where's the repos, Prd?: I host all my repos locally via SSH. Thankfully, git =/= github. If you are interested in any specific pull, please send an e-mail to...; KenshiDBdotWiki@gmail.com; I can be contacted here and will get back to you within a day - I keep tabs on all my e-mails thanks to work habits.; Is the wiki's autmoated mail server active?; Not yet - some remaining questions on Auth. It'll probably stay as Gmail for convenience.