I've added documentation to https://agora.nasqueron.org/Operations_grimoire/FreeBSD#PostgreSQL without real conviction.

Fixed. Form works again.

I'm rebuilding PostgreSQL 15.4 with XML support on db-A-001.

Jan 14 23:13:52 db-A-001 postgres[35351]: [7-1] 2024-01-14 23:13:52.659 UTC [35351] ERROR: unsupported XML feature

When upgraded to FreeBSD 14, we lost this.

When clicking to Save Progress:

Added RHEL question.

In T1924#28790, @dereckson wrote:

router-001 update would cut network connections between Ysul, WindRiver, CloudHugger and IntraNought VMs.

I think that's actually acceptable, as production services can reach web-001/db-*/ directly through their dedicated network card.

Impact:

• IRC bots wouldn't be able to reach MySQL or Vault as they're still on Ysul
• Services still on Ysul can't reach
• Development servers can't reach production services, or Dwellers

Another issue is we lose connections to all those machines, as router-001 is used to route traffic to them.

Probably best to ship router-002 under FreeBSD 14 so we can prepare to minimize this impact if we need more hypervisors in the future.

router-001 is out of scope as long as T1939 is implemented

router-001 update would cut network connections between Ysul, WindRiver, CloudHugger and IntraNought VMs.

Complector done.

done for db-B-001

Done for Hervil

WindRiver done last week. Works perfectly fine.

Situation has evolved since 2017, we currently configure nginx with TLSv1.2 + TLSv1.3,
per Mozilla intermediate configuration https://ssl-config.mozilla.org/

Ubald configuration is deemed out of scope of devserver validation.

whom-diff isn't provided anymore

We can specify the default shell in user accounts configuration.

Even with correct SRV records, no HTTP request reach nginx, neither on www1. or packages.

Comparing to pkg.pfsense.org, we only use subdomains, not full domains:

This is a blocker for the use of pkg.

A certificate for mail.nasqueron.org and hervil.nasqueron.org has been generated successfully after D3248 has been deployed:

Documentation for HTTPS isn't clear, perhaps we should check the pkg source code for the exact seek.

DNS record according the documentation:

We don't maintain anymore an ownCloud installation nowadays, but we're interested to recreate a NextCloud instance, with backup.

trip available on WindRiver.

trippy has now a FreeBSD port available since 2023-04-25 according https://www.freshports.org/net/trippy/

@fauve What do we need to move forward on this task?

Phabricator uses this:

T169 / D3168 seems to work