[ Priority high, as it's a blocker to switch ready sites - like MediaWiki and the static ones - to Alkane ]

We need to figure how to express the idea "GW isn't in our prefix" to use that syntax
instead of the more straightforward "ipv6_defaultrouter=..." which is the current Salt config.

With proper route configuration, I've in/out IPv6 connectivity for web-001 with OVH native IP.

Experiments with native OVH IPv6 aren't good

[ Avoid cookie-licking ]

Note for lyrics, we're correctly writing in UTF-8 to the database, so this bug isn't related.

Some ideas for a WordPress SaaS to consolidate and maintain our different WordPress installations:

The role webserver-alkane instead of the role webserver-legacy can be deployed to WindRiver.

Flood is so high nowadays that we can need systematically to use | grep -v sshd.

We've adopted it in rOPS and it finds insecable spaces put inside {{ }} instead of regular spaces at least.

• MySQL at db-B-001 is ready, with tooling to migrate databases from Ysul
  • Consolidate the nginx configuration across all the roles, to have a common basis in webserver-core
  • Easter week-end was the opportunity to write T1826, a Rust tool to help sites deployment