Local development improvement #311
Labels
CI
Continuous Integration and release process
documentation
Improvements or additions to documentation
good first issue
Good for newcomers
Summary
A single node docker based development environment that is developer friendly.
Problem Definition
Right now it's very easy to integrate with
make localnet-start
. The reasons for this is because it starts upprovenanced
with docker and provides some developer friendly utilities such as having a large pool ofnhash
in the genesis. P8e for instance can launch this and then easily import a key and transfernhash
to it.The problem with this is that
localnet
is not ideal for local development of dependent services. It is heavy weight for a laptop and in heavy load scenarios the block cut time quickly starts to increase. I'm hopeful this is mostly due to running the full setup on a laptop.Using the single, native provenance setup is not ideal for someone developing dependent services that already make use of docker because you then have to manage the stopping and starting of the native binary in scripts. We were doing this previously, but it's more error prone.
Proposal
A make target that spins up a single node provenance environment making use of a docker image with a sensical genesis file (loaded with
nhash
).Taking this a step further it might even be valuable to have a few documented hardcoded mnemonics associated with addresses that have
nhash
as part of the genesis as well. This would remove the need for dependent services to launch the development environment and then have to create/import keys and transfernhash
as part of a one time setup script. I assume this step is mimicked in most dependent systems that start a local development provenance environment.For Admin Use
The text was updated successfully, but these errors were encountered: