strategy for testing the production knock notifications.

[burtonator]

Describe the bug

Wanted some advice.

I'm trying to verify Knock push notifications config but I can really only test a specific environment. I can test development, frack, or production.

I've already tested development and I know that works with Safari and Chrome push notifications. Including on the phone. The development works fine. I tested that before.

Production is the one I can't test and I need to verify.

• I've tested the 'development' Knock mode with push notifications on desktop + phone on Safari and Chrome and all configurations worked.

• I discussed with @timolegros and we'd like to use a real/production database env rather than the same ones on staging.

Here's the main issue.

The knock backend env uses a different database with different UIDs so configuring it for the production knock instance but using different UIDs wouldn't really work.

It could also "corrupt" our knock config by adding wrong UIDs into Knock.

I think the best thing to do is to push this to production, then debug on production.

The worst thing that would happen is someone tries to turn on push notifications, and it doesn't work. However, we could just focus on this first thing.

The other idea is to configure knock to use the production DB as well as production Knock env.

I think we would only need to change the DB URL for that? I haven't done this before though.

@timolegros @ilijabojanovic

Initial conditions

Environment:

Branch/Release version:

Browser:

Wallet:

Reproduction steps

Actual behavior

Expected behavior

Screenshots / Video

Reporter

Additional context

[timolegros]

If development works I'm fine with just debugging in prod especially since we have the feature flag we can just toggle if it doesn't work.