Package: difuzio-mariadb
Source: difuzio
Version: 0.6.2
Architecture: amd64
Maintainer: Eric Seigne <eric.seigne@cap-rel.fr>
Installed-Size: 16043
Depends: adduser, init-system-helpers (>= 1.54~), systemd
Recommends: ca-certificates
Suggests: difuzio-webui, mariadb-server, postfix
Conflicts: difuzio-server
Replaces: difuzio-server
Provides: difuzio-server
Homepage: https://doc.cap-rel.fr/difuzio
Priority: optional
Section: mail
Filename: pool/main/d/difuzio/difuzio-mariadb_0.6.2_amd64.deb
Size: 4987180
SHA256: e5b8df881e6dbcb32921c185e90859aec719d3f711a2d9db9ff24dd2664d9867
SHA1: 49403ea0d0a56ebfaf61506e27a6002be96c20a3
MD5sum: dc7ffc6c40055fee625635f15b1541da
Description: mailing list and newsletter engine (MariaDB backend)
 difuzio (DIFfusion Unifiée vers Abonnés) is a mailing list and newsletter
 engine: LMTP reception, posting pipeline (authorisation, transforms, DMARC
 munging), outbound delivery with VERP bounce attribution, RFC 8058 one-click
 unsubscribe, bounce and feedback loop handling, a REST API and a web console.
 .
 This package carries the server built against MariaDB 10.6 or later, which
 coordinates every process through row locks and advisory locks. It is what a
 multi-host or high volume installation needs. The three daemons (serve-web,
 serve-lmtp, worker) are one binary, shipped with their systemd units and the
 migration oneshot.
 .
 It is mutually exclusive with difuzio-sqlite: an installation runs one backend,
 and a database is not convertible from one to the other.

Package: difuzio-sqlite
Source: difuzio
Version: 0.6.2
Architecture: amd64
Maintainer: Eric Seigne <eric.seigne@cap-rel.fr>
Installed-Size: 19272
Depends: adduser, init-system-helpers (>= 1.54~), systemd
Recommends: ca-certificates
Suggests: difuzio-webui, postfix
Conflicts: difuzio-server
Replaces: difuzio-server
Provides: difuzio-server
Homepage: https://doc.cap-rel.fr/difuzio
Priority: optional
Section: mail
Filename: pool/main/d/difuzio/difuzio-sqlite_0.6.2_amd64.deb
Size: 6176360
SHA256: 80ee763b4811f8e4b4c79fc32e82000d09bce386f0863c1dd1cb68d89b6105ea
SHA1: 5be74981966f6ba946a5b0b84709199c3a54f771
MD5sum: 66405db8095a02b0a8654c74b2a54bff
Description: mailing list and newsletter engine (SQLite backend)
 difuzio (DIFfusion Unifiée vers Abonnés) is a mailing list and newsletter
 engine: LMTP reception, posting pipeline (authorisation, transforms, DMARC
 munging), outbound delivery with VERP bounce attribution, RFC 8058 one-click
 unsubscribe, bounce and feedback loop handling, a REST API and a web console.
 .
 This package carries the light server: one SQLite file under
 /var/lib/difuzio, no database server to administer. It suits a single-host
 installation of modest volume; beyond that, and for any multi-host deployment,
 difuzio-mariadb is the backend to use. Installing this package creates the
 database, applies the schema and starts the stack, leaving only the first
 administrator to create.
 .
 It is mutually exclusive with difuzio-mariadb: an installation runs one
 backend, and a database is not convertible from one to the other.

Package: difuzio-webui
Source: difuzio
Version: 0.6.2
Architecture: all
Maintainer: Eric Seigne <eric.seigne@cap-rel.fr>
Installed-Size: 743
Suggests: difuzio-server, nginx | apache2 | httpd
Homepage: https://doc.cap-rel.fr/difuzio
Priority: optional
Section: mail
Filename: pool/main/d/difuzio/difuzio-webui_0.6.2_all.deb
Size: 183556
SHA256: c6cfc66463e1ca91e22d07b93d125f6b116939def4ec05947e916d6fcdf42a58
SHA1: 38c9a7064e35864c648ca102d1b48450b961ed92
MD5sum: 3fd8a9e3c4f52e0339edf067da807282
Description: mailing list and newsletter engine (admin console)
 difuzio (DIFfusion Unifiée vers Abonnés) is a mailing list and newsletter
 engine. This package carries the administration console: a static bundle in
 /usr/share/difuzio/webui, served by the front proxy on the same origin as the
 REST API it talks to.
 .
 The console is never compiled into the server binary and is not tied to the
 host running it: a proxy on another machine can serve it just as well. It does
 report which build it is, next to the version the server reports, so an
 operator can see whether both halves were deployed together; that comparison
 only holds when both come from the same release.