Simapp Localnet

[alexanderbez]

Description

Drop-n-lift localnet functionality from Gaia. So we no longer have to rely on Gaia.

closes: #6418

---

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

• Targeted PR against correct branch (see CONTRIBUTING.md)
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
• Code follows the module structure standards.
• Wrote unit and integration tests
• Updated relevant documentation (docs/) or specification (x/<module>/spec/)
• Added relevant godoc comments.
• Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
• Re-reviewed Files changed in the Github PR explorer

[codecov]

Codecov Report

Merging #6421 into master will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           master    #6421   +/-   ##
=======================================
  Coverage   55.66%   55.66%           
=======================================
  Files         465      465           
  Lines       27674    27674           
=======================================
  Hits        15404    15404           
  Misses      11169    11169           
  Partials     1101     1101           

[tac0turtle]

LGTM, would we want to publish a docker image somewhere?

[alexanderbez]

LGTM, would we want to publish a docker image somewhere?

Why? This is just a simapp used for local testing and integration purposes.

[aaronc]

@alexanderbez just curious, is there a reason we couldn't also do this by spinning off sub-processes instead of docker compose? It seems that would be more portable for other apps. We could have a testnet init command that populates all the directories as in this PR and then a testnet start command that spins off n sub-processes with those configs. What do you think?

[alexanderbez]

There are many many ways you can do this. This has existed before I worked on the SDK and I just simply replicated the process because it works and is simple. I will note that I generally am in favor of Docker (compose) and would prefer to stay that route. App devs can implement this however they wish. The SDK doesn't aim to provide devops tooling.

[alessio]

I will note that I generally am in favor of Docker (compose) and would prefer to stay that route

I agree with this.