Postgres Inbox

Usage

The Postgres Inbox allows use of Postgres for Brighter's inbox support. The configuration is described in Basic Configuration.

For this we will need the Inbox packages for the Postgres Inbox.

• Paramore.Brighter.Inbox.Postgres

private static IHostBuilder CreateHostBuilder(string[] args) =>
    Host.CreateDefaultBuilder(args)
        .ConfigureServices(hostContext, services) =>
        {
            ConfigureBrighter(hostContext, services);
        }

private static void ConfigureBrighter(HostBuilderContext hostContext, IServiceCollection services)
{
    services.AddConsumers(options =>
        {
            var config = new RelationalDatabaseConfiguration(connectionString, "brightertests", inboxTableName: "inboxmessages");
            opt.InboxConfiguration = new InboxConfiguration(new PostgreSqlInbox(config));
            ...
        });
}

...

Provisioning the Inbox Table

You have two equally valid options for creating and maintaining the Inbox table:

Option A — Let Brighter provision and migrate it for you.

Brighter ships a library that creates the Inbox table on first start and evolves its schema across Brighter releases. See Database Provisioning and Configuring Box Provisioning. The PostgreSQL Inbox is at schema version 1 — the table shipped with its final column set, so there are no inbox migrations for this backend to apply.

Option B — Manage the DDL yourself.

Use PostgreSqlInboxBuilder.GetDDL() to obtain the DDL Brighter ships and apply it via your own tooling (FluentMigrator, Flyway, Liquibase, or hand-rolled scripts).

Choose based on fit; neither option is deprecated.