Whitespace issues

Extract TeX live states to tex.sls for clarity. Fix symlink.

For all CARP external documentation, I think I've found the threshold where information is outdated in that man page:

According carp(4) (man carp) examples section, the name has changed.

Procedure still the same in current TeX Live Guide, updated the link.

[ Deassigning, as it needs some CI love first, to be able to run modern Node 24 on Jenkins ]

In a Debian container, this works:

As the eggdrop code supports to run a function periodically with bind time with a syntax similar to cron, it could be interesting too to check server connections health there too.

Need to publish it to Docker Hub, for local tests to create the operations agent image.

Just a note Flow isn't maintained anymore. The current recommended discussions extension is https://www.mediawiki.org/wiki/Extension:DiscussionTools

Provisioning of /etc/anubis/private.key we added here has disappeared: https://devcentral.nasqueron.org/D3908?vs=10478&id=10480#toc

Plan is to replace pip installation by a script, ideally invokable through make, to prepare the venv or anything else with Salt there.

Proof of concept to call OVH API from Python to define MAC address to router-002/003.

At this point, we can consider that the goal "create a wiki farm" is accomplished, and the subtasks are feature requests / bugs to solve in the ongoing cycle.

Will need to be revisited when we switch to acme.sh.

Rebaesd

Testing with shangri-l:

Code responsible to convert the message into a JSON payload, then post it:

@yousra I've noticed I've already created a task with the same issue, with dash character — instead of the non-breaking space here.

Documented on Agora: https://agora.nasqueron.org/index.php?title=Code_conventions&diff=2486&oldid=2039

OVH API credentials published to apps/network/carp-hyper-001-switch path,
under application_key, application_secret, consumer_key keys.

module/resource name

The format of .clang-format has evolved, see P391 for clang-format19.

From upstream:

@Duranzed Can you open the issue with Terminator maintainers, so we can determine the best course of action for the plugin to load our resolve-hash library?