Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: update with feedback from validators #1180

Merged
merged 2 commits into from
Jan 19, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,7 @@ services:
image: "ghcr.io/unionlabs/uniond-release:${UNIOND_VERSION}"
volumes:
- ~/.union:/.union
- /tmp:/tmp
network_mode: "host"
restart: unless-stopped
command: start --home /.union
Expand Down
6 changes: 6 additions & 0 deletions site/src/content/docs/docs/joining-testnet/faq.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,12 @@ Yes, you can find them listed on the [Public Endpoints](../public-endpoints) pag

Ensure you have exposed your host machine's network via the `--network` flag in docker.

### My query commands aren't using values from my client config?

Due to [an issue in the cosmos-sdk](https://github.com/cosmos/cosmos-sdk/issues/18868), commands using AutoCLI do not respect the `--home` flag and instead always try and read the default home. As a temporary fix, we've removed the behavior reading the default home, always require a `--home` flag, and moved all `tx` commands away from AutoCLI. However, `query` commands still use AutoCLI and won't read the `--home` flag.

To get around this behavior, we suggest always supplying `--node` and `--chain-id` when using query commands.

### Other questions?

Please [join our Discord](https://discord.union.build) and ask around in our community.