Substrate Node Template Generator

A tool to generate stand-alone node templates of a customized Substrate clients used in "Substrate Library Extension" (SLE) projects like Cumulus, Canvas, Frontier, as well as any custom chain that intends for users to build off of as a base template included in their source.

Expected Project Hierarchy

This tool is tightly coupled with how a SLE is structured. To use this, your project needs to roughly conform with the style of:

A local template node that has similar structure to the Substrate node template
- (Optional, encouraged) CI that builds against your template to do integration testing. This also assures the
Local pallets defined and added to the template runtime
Local custom logic, like pallets, contained in crates outside the template to enable sourcing them through cargo from an external project.
Source available on a public repo that cargo can use (GitHub is the only supported for now)

Credit

Based heavily on the integrated Node Template Release Tool included in Substrate.

xx network Substrate based blockchain node

xx network Substrate based blockchain node Rust Setup First, complete the basic Rust setup instructions. MacOS users: setup to compile for Linux Befor

11 Dec 20, 2022

The Data Highway Substrate-based blockchain node.

DataHighway-Parachain, a parachain on the Polkadot network. Planned features include a decentralized LPWAN roaming hub for LoRaWAN IoT devices and network operator roaming agreements, participative mining, an inter-chain data market, and DAO governance.

11 Dec 2, 2022

Comments

converts dependency tables to inline tables

Converts Cargo.toml dependency tables from dotted (each key is on its own line) to inline tables e.g. codec= { default-features = false, features = ['derive'], package = 'parity-scale-codec', version = '3.0.0' }.

opened by peterwht 1
Set a local path for the upstream repo, have this pull he requested branch/tag/rev to use

If you have a local copy of the upstream repo, this can be set with a local path. If you do not, this path will be used to clone the repo from upstream at only the depth of the branch/rev/tag specified. In both cases, we pull from the origin to ensure we have the most updated reference.

Then execute the rest of the generation from this.

opened by NukeManDan 1
Lean into methodology of `diener`
https://github.com/bkchr/diener/

This tool is also close to the features of this template. Notably the things needed to use it in place of this tool:

A way to specify path dependancies to be replaces in context of the template:

The root-dir of the overall upstream, plus the woking-dir of the template, and anything outside the working-dir would need to be replaced by the git dependency with a specific branch/rev/tag specified.
opened by NukeManDan 0