feat: Script for starting a local Regen test node, based on the tutorial

[frumioj]

Description

Added a script that runs most of the commands shown in the tutorial https://docs.regen.network/getting-started/ to make starting a node quicker than running the commands individually. If a command fails, the script errors and ends.

Two command-line options are allowed for specifying a keyring-backend (-k), and the name of the blockchain (-c).

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• followed the guidelines for building modules
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[codecov]

Codecov Report

Merging #538 (b82182c) into master (8972c48) will increase coverage by 0.21%.
The diff coverage is n/a.

❗ Current head b82182c differs from pull request most recent head 03a60fc. Consider uploading reports for the commit 03a60fc to get more accurate results

@@            Coverage Diff             @@
##           master     #538      +/-   ##
==========================================
+ Coverage   75.72%   75.94%   +0.21%     
==========================================
  Files         105      105              
  Lines       14183    13829     -354     
==========================================
- Hits        10740    10502     -238     
+ Misses       2825     2709     -116     
  Partials      618      618              

Flag	Coverage Δ
experimental-codecov	75.94% <ø> (+0.21%)	⬆️
stable-codecov	67.30% <ø> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

[blushi]

I'm not sure if we need this since there's already some testnet command built-in cosmos-sdk

[frumioj]

I'm not sure if we need this since there's already some testnet command built-in cosmos-sdk

I merely intended to duplicate what is done in the Regen "Getting Started" doc (https://docs.regen.network/getting-started/). I'd also note that I personally very often start over with a brand new node configuration, so I was often repeating the same steps while doing development.

If the testnet route is the way, perhaps this should be noted in the "Getting Started" doc?

[ryanchristo]

Thanks for the pull request @frumioj!

If the testnet route is the way, perhaps this should be noted in the "Getting Started" doc?

Yes, this should be noted in "Getting Started" but the testnet command is not yet implemented. I opened #563 for tracking. We could use this script in the meantime.

[ryanchristo]

I'm receiving the following error when running the script:

./scripts/start_testnode.sh: 47: Syntax error: ";;" unexpected (expecting "fi")

It looks like two instances of exit ;; should be exit 1.

Also, $OSTYPE is not working for me on the latest version of Ubuntu (I receive linux-gnu: command not found when checking $OSTYPE). After doing a little research, it looks like and using uname instead of $OSTYPE might be the best solution.

Otherwise this looks good. I wouldn't be opposed to including it as a temporary solution until we have the testnet command up and running.

[frumioj]

Thanks @ryanchristo 👍

[ryanchristo]

tACK

bash ./scripts/start_testnode.sh

One more request to update #!/bin/sh to #!/bin/bash. We use #!/bin/bash in other scripts and it will eliminate the need to specify bash when running the command.

Pre-approving. Thanks again!

[blushi]

Thanks for the pull request @frumioj!

If the testnet route is the way, perhaps this should be noted in the "Getting Started" doc?

Yes, this should be noted in "Getting Started" but the testnet command is not yet implemented. I opened #563 for tracking. We could use this script in the meantime.

Right, I didn't realized this was only done on cosmos-sdk simapp!

[blushi]

tACK, thanks @frumioj!