Change default network to local
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- docker, shell
- Domain
- developer-experience, devops
Research direction
Review the quickstart image's startup path for the no-parameter case, and compare its behavior with the stellar-cli stellar container start command, which already defaults to local mode. Done means an unconfigured image starts on the local network and users can explicitly select testnet with --testnet.
Written by the indexing model from the issue text.
Description
I think the default network of the image should change from testnet to local.
This will be a breaking change.
Why:
The quickstart image is primarily intended for use during development and testing. It's defaults should operate to serve that purpose. When folks are testing they typically test either against the public test network or a local network. When testing against the public test network the easiest path to access is to approach is to communicate directly with the SDF hosted testnet RPC at https://soroban-testnet.stellar.org or the SDF hosted testnet Horizon at https://horizon-testnet.stellar.org. The quickstart image only adds value to setup when running a local network.
Today the image when started without any other parameters defaults connecting to testnet. This means for the default common case a developer needs to read the docs and pass additional parameters.
The stellar-cli has a stellar container start command that defaults already to starting the container in local mode for the same reason.
Impact:
For anyone using this image without parameters to connect to testnet, they will see the container instead connect to local and will need to add a parameter --testnet.
cc @stellar/devx @janewang
- Dominant language
- Shell
- Stars
- 222
- Forks
- 236
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 12
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stellar/quickstart
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
stellar/quickstart#932 · 16 comments · 2 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 58/100
stellar/quickstart#923 · 2 comments ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
stellar/quickstart#911 · 2 comments ·
-
feature request
Difficulty 5/5 Over a week Newbie friendliness 35/100
stellar/quickstart#907 · 1 comment ·
-
feature request
Difficulty 5/5 Over a week Newbie friendliness 35/100
stellar/quickstart#906 · 3 comments ·
All issues in stellar/quickstart
Similar issues
-
Update Vish to 1.1.5 Openpackage-update
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oSoWoSo/vOid_Community_repOsitory#144 · 1 comment ·
-
help wanted new command
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
tldr-pages/tldr#24151 ·
-
PacReq: Rune IDE Openpackage request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pacstall/pacstall-programs#9402 ·
-
[BUG] ci: the first prefetch-images.sh call runs before shard.txt exists, so it is always a no-op Openbug github-actions
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
update-request
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
msys2/MINGW-packages#31768 ·