Revisit wasmd setup doc

[alpe]

People report issues with the env setup from the docs on the cosmwasm discord or github.
The whole "Setting up ..." should be revisited to make it work on all machines.

The "client config" module was added back to the SDK and wasmd long time ago. This may provide a more resilient setup config and can avoid the unsafe source <internet. Please see the wasmd config command

See https://stackoverflow.com/questions/72051270/cosmwasm-environment-setup-error-first-path-segment-in-url-cannot-contain-colo/73487969#73487969

Tag: Error: couldn't get client from nodeURI: parse

[findolor]

@alpe wasmd config does not have other flags defined. We still need to get other transaction related (gas-prices, gas, gas-adjustment, ...) flags for sending out TXs.

We can configure chain-id and node but cannot change these flags. Our best option is to pull it from a repo.

[findolor]

This is also made for zsh, that's why some people using bash are having problems with NODE and TXFLAGS. They still need to export them after sourcing.

@orkunkl Maybe It might be worth to have two different env files for zsh and bash?

[MightOfOaks]

@alpe - Would it be an option to add news keys to the client config in Cosmos SDK for the remaining flags?

[alpe]

Would it be an option to add news keys to the client config in Cosmos SDK for the remaining flags?

The client config comes from the SDK. Best would be to make a PR to their repo to add the values you need.
When introduced proper, I think the gas params to calculate the fees don't need not be hidden: --gas-prices 0.25umlg --gas auto --gas-adjustment 1.3. This is what people would need to setup anyway when working with other chains.
But this is just my opinion.