Alkane doesn't need any new account. We can send a request to an URL and it will be run by the deploy user.

Here we are with D3812 build:

That builds properly:

In T1098#21963, @dereckson wrote:

Tested a build manually successfully with:

$ git clone https://github.com/Learath2/sBNC.git
$ cd sBNC
$ cc *.c -o sbnc
$ sudo cp sbnc /usr/local/bin

Claude Sonnet artifacts

We switched to a dynamic approach for init.sls in D3334.

The full /etc/nginx directories on both docker-002 and dwellers use httpd_config_t for every file.

It's now available on bash by default, but still missing for zsh.

Could have been interesting to add more context on this.

Pending new build of 15.9 version.

Same thing for Dwellers:

During WindRiver reprovisioning, the network unit behaved correctly.

Consolidation recent works occurred at T1828 to further unify nginx configurations.

Some context about this staging repository:

[Moved to T1620]

That's an issue for Chrome to report upstream.

Priority is high as it can affect our certificate renewal process.

Portsnap is deprecated, we'll switch to a Git repository.

Are we going to keep the rSTAGING repository?

Crossed-out files no longer needing Shellcheck.

Per previous comment, I'd advice to downgrade to 3006 LTS for paas-docker servers too.

I've also discovered we can't deploy secrets to Salt 3007+ anymore from a Salt 3006 server: