I confirm the workflow works well.

The workflow itself has never really been the problem. It's fine, and it maps closely enough to a GitHub PR loop. What's heavy I would say is how much arrives at once on the first contributions, it's equal to too much current for a wire.

Created object storage too.

Let's close this part of the work. We'll add credentials to Vault and OVH API afterwards (WIP from https://devcentral.nasqueron.org/D4191?id=10994).

Update syntax

Fix syntax

Clean commit to only create swift/s3 bucket

A. Keep access

D4190 has been deployed.

@yousra if we define a block like this at node level:

In addition to this change, we also need to reuse our dedicated IP address for e-mails:

A. Keep access

Coherent variables names

strtolower

s/array_map/Vector::map/g

Rebased against D4189.

Eat your own dog food stamp of approval.

Avoid count directories. Handle IO errors.

More tests

Cohort 1 accounts have been successfully removed from Dwellers.

Security access clean-up for inactive users

GPT-5.6-Sol proposal: https://chatgpt.com/share/6a8a838d-4cbc-83eb-b59e-5d847a64b03e

A-Keep acces - Anubis tester

Best short-term solution, to allow mail from Docker services too, is to allow the new router IP.

GPT-5.6-Sol idea:

Confirmed: Phabricator deliberately uses its default no-reply address as a recipient on some notifications. As Postfix currently rejects that recipient before DATA, we’ll declare notifications-noreply@devcentral.nasqueron.org as a valid blackhole mailbox and silently discard mail delivered to it.

Tests pass: