Wikitech-static is documented here: https://wikitech.wikimedia.org/wiki/Wikitech-static
Right now it syncs via a cron running on the wikitech host (cloudweb*). That job, or something similar, will need to be implemented someplace to consume the new k8s-hosted wikitech and provide it to wikitech-static.
Alternatively, we could entirely re-engineer wikitech-static to be a static site that does some kind of recursive pull from public wikitech. If we coupled that to T304688 (moving wikitech-static to a new VM) then this could be done at any time, ideally prior to the k8s migration. Unfortunately I haven't figured out a way to make such a static site searchable.
UPDATE 3 Oct 2024
After switching Wikitech to k8s, we had to move faster as to ensure wikitech-static remains up to date.
other dumps
Our dumps/snapshot infra already has support to run systemd timers which run dump-related scripts, for a number of miscellaneous services .
Those dumps in turn are publicly served under dumps.wikimedia.org/other/. It makes sense to make wikitech's dump yet-another-other dump.
Why?
- wikitech's dumps are now not a snowflake, but we are reusing processes/code that already exist and work
But dumps 1.0 will be deprecated!
- It is ok, the same solution that will work for all the "other" dumps, will work for wikitech's dump as well.
