Merged.

fantoir2db is now fantoir-datasource

Remove test limit

A lot of code to handle exceptions, mainly because there are
several formats used to represent the FANTOIR code.

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.

"The notification lifecycle: how a notification is provided and consumed" schema

Extract run_multiple_queries method to the db module. We can't easily move the create_table function, as it needs schema-dependant replacement.

Switch to subcommands pattern (like git), so we can extend it

Creation date can be unknown, add code_fantoir to help cross data with other db, fix last line record parsing

Draft implementation: rFANTDB59128e4bfd41 (needs to add all FANTOIR field).

https://about.staging.gitlab.com/blog/2016/03/18/fast-search-using-postgresql-trigram-indexes/ makes me think a Postgresql table with with those GIN trigram indexes would be a better idea than json documents 🤔

nasqueron/rust-musl-builder:nightly published, and we can build the image with that

Notification format: see T771

Tested with RUST_LOG=info so we can also check env logger update in action.

I tried to compile a previous version of the API.

Hotfixed on Ysul with a sudo -u deploy composer update, works in production.

Relevant error file is /var/log/www/nasqueron.org/api-php.log on Ysul: