This is still needed for acme.sh if we want to provision different *.nasqueron.org certificates on different servers.

Really blocked by T1602 if we want to have this on any server without copying private keys around.

The problem is somewhat fixed by two things:

That's an issue for Chrome to report upstream.

Local cache is OK.

Salt SELinux module issue

SELinux context was the default for anything created under /var, which we didn't allow and aren't interested to allow for nginx.

Authoritative DNS

DNS change

For RHEL 8, we probably only need docker-processes, but roles/paas-docker/devel refers dive too.

Those two are indeed authoritative:

Done at the console, but DNS records aren't instantaneously updated, and I'm not even sure those are authoritative (they are for poneytelecom.eu):

2024-10 plan:

Choose to only support FreeBSD:14:amd64 ABI or to use /${ABI}/ in path

We also need a monitoring script to detect those cases:

I've tested poudriered but bump on {"type":"error","message":"Expecting a string for the arguments"} with testport

In T2037#30771, @dereckson wrote:

❌ https://windriver.nasqueron.org/poudriere/base14-dereckson_dev/2024-10-05_12h25m58s/logs/errors/roll-2.6.1.log

❌ https://windriver.nasqueron.org/poudriere/base14-dereckson_dev/2024-10-05_12h25m58s/logs/errors/roll-2.6.1.log

Taking db-A-001.

Message from acme.sh-3.0.9:

https://github.com/acmesh-official/acme.sh/wiki/Stateless-Mode

Yes, it's a fork from Vault 1.14 so we've all the features of token generation. back to the shorter s. tokens).

• about the UI it could be usefull managing secrets more easyly