In D4035#63113, @dereckson wrote:

OK with pillarize too?

OK with pillarize too?

If we're going to flood /var/log/messages with carp debug information, perhaps should we create a separate log topic, but that can be another change. I've created T2292.

Two actions to fix:

The nginx configuration doesn't seem the same for the Docker container and the development site:

I've asked upstream for advice how to resolve pillar for another server than the current node @ https://groups.google.com/g/salt-tower/c/XEKg2CEiZrU

The output is really useful to avoid to manually repeat the ports.

Rebased. Fixed pillar handling.

In D4026#62889, @dereckson wrote:

Note: we're deploying a third secret for CARP routers scripts. If we've already that code merged, we'll need to append a line to deploy that state too.

Note: we're deploying a third secret for CARP routers scripts. If we've already that code merged, we'll need to append a line to deploy that state too.

Next: try salt web-001 paas_docker.get_upstreams

Rebased against current main for Alkane.

This change is interesting and should be rebased.

This configuration is for Pixelfed old versions.

Not sure today if we still want to deploy through Docker, or if we would target Alkane PaaS for Espace Win sites. It's also unknown if it brings value to put back the forum archive.

Currently, zed51.dereckson.be serves a 500 error.

Tried to deploy on DevCentral - it's now an old container still using PHP 7.4.

We can consider the mail server as deployed and create tasks for extra actions in the Mail projects.

@DorianWinty Do we have everything in the configuration or is there some actionnables remaining?

Deployed and working fine.

Dovecot deployed and working well.

[ Resetting assignee of long-assigned tasks. Feel free to reassign when working on this. ]

With Salt, sudo files content are now managed from rOPS.

Not a priority right now, as we use Alkane to trigger website deployments.