Skip to content
This repository has been archived by the owner on Oct 7, 2020. It is now read-only.

Write a guide that explains and simplifies connecting to our testnets #179

Closed
1 task
adrianbrink opened this issue Jun 30, 2017 · 7 comments
Closed
1 task
Assignees

Comments

@adrianbrink
Copy link

adrianbrink commented Jun 30, 2017

Currently connecting to the testnets requires you to follow a specific blog posts.

There needs to be documentation (see #225 for more information on docs) that explains how to connect to the testnets.

Furthermore, it should be very quick and simple to connect to the testnets after having installed ethermint. There should be cli commands and flags that automatically connect you to a certain public ethermint network.

  • Test it with 2 users that have never used ethermint or venus and just watch them follow the guide. Then update accordingly
@adrianbrink adrianbrink changed the title Simplify connecting to VENUS through an init.sh script and a start.sh script Simplify connecting to our testnets Aug 14, 2017
@adrianbrink
Copy link
Author

@odeke-em What do you think about extending the CLI to actually cover the use case of connecting to one of our testnets?

@adrianbrink adrianbrink changed the title Simplify connecting to our testnets Explain and simplify connecting to our testnets Aug 14, 2017
@adrianbrink adrianbrink added this to the 0.5.0 milestone Aug 14, 2017
@odeke-em
Copy link
Contributor

SGTM! I can take a look at this when I get up, thanks.

@adrianbrink adrianbrink modified the milestones: 0.6.0, 0.5.0 Aug 14, 2017
@zramsay zramsay self-assigned this Aug 16, 2017
@zramsay
Copy link
Contributor

zramsay commented Aug 17, 2017

just a thought: ethermint init could have a flag --testnets that generates the required files. tendermint init could have the same feature, so we can skip the git clone the-testnets-repo and cp sequence. would be an extension of #245

@adrianbrink
Copy link
Author

The idea is that we hardcode the genesis files for tendermint validators and ethermint into the binary. When you then specify ethermint start --testnet --home ... ethermint initialises with the testnet genesis file and overrides the genesis file for tendermint.

Let's also consider that we start tendermint automatically in the background by using https://golang.org/pkg/os/exec/ to issue tendermint init --home and tendermint node.

@adrianbrink adrianbrink changed the title Explain and simplify connecting to our testnets Write a guide that explains and simplifies connecting to our testnets Aug 20, 2017
@odeke-em
Copy link
Contributor

odeke-em commented Aug 20, 2017

@adrianbrink the tricky thing that am thinking about doing #179 (comment) is that what if the user doesn't want to reinit tendermint?
A solution to that is to add an opt-out flag say --no-tendermint which will be documented to opt out of invoking tendermint init when ethermint init is invoked and tendermint node when ethermint is invoked. I think the new cosmos-ui by @mappum et all currently invokes both baseserver and tendermint

@adrianbrink
Copy link
Author

The flag should be --without-tendermint to be consistent with the rest of the apps.

@zramsay
Copy link
Contributor

zramsay commented Aug 24, 2017

the original issue is merged

@zramsay zramsay closed this as completed Aug 24, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants