2025-02-05 ops office hours take:

• Mailgun could be used as fallback for certificates issue
• We need to update payment info at Mailgun to reactivate service in that case, as our account isn't active anymore

Upgrade to FreeBSD 15 broke Dovecot, needed to be recompiled.

@DorianWinty It seems it tries to use Mailgun again instead of mail.nasqueron.org SMTP, could we prune the Mailgun part of the configuration? I removed DevCentral from the admin panel there.

One repository doesn't have a call sign.

Have worked fine all summer.

After arc land is successful:

Next one detected during arc land:

Next one:

Decreased priority as it was on my local laptop, WindRiver is still 8.3.16.

First part done,

Should use port 587 for submission. Port 25 (smptd) should be server-to-server only.

Jan 6 19:04:10 hervil postfix/smtpd[73868]: connect from docker-002.nasqueron.org[51.255.124.9]
Jan 6 19:04:12 hervil postfix/smtpd[73868]: warning: docker-002.nasqueron.org[51.255.124.9]: SASL LOGIN authentication failed: (reason unavailable), sasl_username=devcentral
Jan 6 19:04:12 hervil postfix/smtpd[73868]: lost connection after RSET from docker-002.nasqueron.org[51.255.124.9]
Jan 6 19:04:12 hervil postfix/smtpd[73868]: disconnect from docker-002.nasqueron.org[51.255.124.9] ehlo=1 auth=0/1 rset=1 commands=2/3

Reported upstream: https://we.phorge.it/T15953

The documentation is now more comprehensive and include the steps to contribute.

Development switched to https://chaoss.github.io/grimoirelab/

That workflow has been added to the main documentation page.

code.nasqueron.org with Hound is stable enough to close this task.

@Ash-Crow @fauve @rama @replicatorbe @Sandlayth @xcombelle Any feedback on this?

https://github.com/nasqueron/arcanist/commit/1a7912af24a7feaeb18057a4faef733cc115057b

Documentation available at https://devcentral.nasqueron.org/w/setup_2fa/

2FA enabled

This visualisation doesn't satisfy our goals.

Rebased against upstream, works like a charm on WindRiver.

https://devcentral.nasqueron.org/feed/7214929457763397007/

Next: publish this somewhere

Done immediately after this task. We now receive correctly Phabricator events on RabbitMQ.

I've regenerated /usr/share/ca-certificates and /etc/ssl/certs based on a "recent" Debian ca-certificates package against Debian Sid, version 20211016. Works like a charm now.

Container still runs on Jessie, we need to deploy new @DorianWinty work on recent Debian PHP 8 container, with correct certificates.

Disabled Sentry, so we can have a correct log of the stacktrace, and updated description accordingly.

I'm not sure can still a reliable way create a map between project PHID and name. That should be the first thing to investigate.