[Feature]: Standalone Docker Image can have Mainnet Schemas Deployed

[wilwade]

Feature Description

Details

When developing an application on Frequency, you often want to have the schemas from mainnet deployed to make use of.

This proposes that there is either a new image, or an option on the standalone-node image to have mainnet schemas be deployed at launch.

Options

• Launch time pull: Pulls the mainnet schemas when the image is first launched
• Build time: Create a separate tags:
  • frequencychain/standalone-node:v1.12.0-schemas{n} where n is the max schema id
  • frequencychain/standalone-node:latest-schemas
  • Requires CI to look for new schemas every (hour?) and build new images when schemas are created on mainnet (or triggered with workflow_dispatch)

AC

• [ ] Image should have all mainnet schemas deployed
• [ ] Image should have all mainnet schema names correctly set
• [ ] Tag should be published (if needed) to docker hub
• [ ] Image Readme should include the additional details of the new options

Searched for Related Issues

• [X] I have done a search for related issues and either found none, or noted them

[wilwade]

Update:

I have code that can pull the schemas and use sudo to set storage on the chain.

Current Options:

• Add node to the dev image and just run this script at start if a flag is set to do it.
  • Bad: Requires node in the dev image
  • Bad: Requires network connection at start (slower time to healthy)
  • Good: Easy to do and requires NO additional images or tags
• Offer an image on top of the image that does the same as ^
  • Meh: New image/tag, so doesn't require node in the root image
• Update the schemas pallet to take a genesis config
  • Could then setup the genesis config to have or pull in the json of the existing mainnet schemas
  • Good: Simple setup and allows for easy addition of other schemas
  • Good: Can build a script that would update the schema data
  • Bad: Complex
  • Bad: Requires commits to main and release of the new image for the new schemas to be there
  • Meh: Always has the mainnet images. No option without them
• Create a raw spec for dev and inject the storage keys and values
  • Messy, and unclear what is happening. Rejected.
• MAYBE: Can we do the genesis config, but have the json be injected post build
  • I think so. Then it could be a build step or be a pull at runtime start

[wilwade]

MAYBE: Can we do the genesis config, but have the json be injected post build

So possible, but requires writing out to the raw spec and manipulating that before reading it back in. Really nasty and not a good option.