Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BE] Deprecate current hypercerts supabase instance in favor of hypercerts-staging #1305

Open
Jipperism opened this issue Apr 15, 2024 · 1 comment

Comments

@Jipperism
Copy link
Contributor

What is it?

Once the revamped frontend is online, we should deprecate our current supabase instance. Reason for doing so is it's not migration-based so a liability. It also carries a lot of technical debt.

Steps:

  • Double check with all team members which tables are relevant, and which can be thrown away (see also discord discussion
  • Move over table structure, into migrations for hypercerts staging
  • Move over data
  • Run a modified version of the claim id update script (scripts/update-claimids-in-supabase-to-multichain.sql)
  • Update defender tasks:
// defender/src/auto-tasks/batch-mint-claims-from-allowlists.ts
  const formattedClaimIds = claimIds.map(
    (claimId) =>
      `${network.chainId}-${contractAddress}-${claimId
        .toString()
        .toLowerCase()}`,

// defender/src/auto-tasks/mint-claim-from-allowlist.ts
  const formattedClaimId = `${network.chainId}-${contractAddress}-${claimId

// defender/src/auto-tasks/on-allowlist-created.ts
    claimId: `${network.chainId}-${contractAddress}-${tokenId}`,
  • Update supabase instance in marketplace sdk
  • Update supabase instance in hyperboards
  • Update supabase instance in starter apps
@bitbeckers
Copy link
Contributor

New supabase-staging setup for reference: https://github.com/hypercerts-org/hypercerts-indexer/tree/develop/supabase

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

2 participants