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

Process for approving a metafactory or nft #64

Open
Geimaj opened this issue Aug 31, 2022 · 0 comments
Open

Process for approving a metafactory or nft #64

Geimaj opened this issue Aug 31, 2022 · 0 comments

Comments

@Geimaj
Copy link
Contributor

Geimaj commented Aug 31, 2022

We have, instead of migrations, a file for each insert/approval as well as a corresponding processor, so for example:

eg:
upserts.json
{
nftid1: {type: nft, upsert: {approved: true}}
factoryid: {type: nftfactory, upsert: {approved: true},
}

inserts.json
{

}

insertsProcessor:

  • run through all inserts that do not exist, and then apply them

upsertsProcessor:

  • runs through all upserts and applies them
  • for upserts, they should be processed in order and the index of the lastProcessed upsert is stored in the processor so that it automatically resumes when we add new stuff

Last TBD question:

  • The above design will still require a commit and push and deploy to upserts.json, how can we improve this so that just a simple admin api/ui achieves the same purpose?
  • Answer: Defer to next feature, but the above schema should be sufficient wherever stored
@Geimaj Geimaj moved this from Next Todo to In Progress in Spindexer Main Sep 1, 2022
@Geimaj Geimaj moved this from In Progress to Done in Spindexer Main Sep 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

1 participant