Implementing a command to spin up a faucet server

[lumtis]

Currently, c serve spin up a faucet server along with the chain with the faucet account in config.yml.

Some testnet started outside of serve, like a testnet bootstrapped with Ignite Network commands, might also require a faucet.

I'm suggesting adding a new namespace faucet for every faucet related feature

ignite faucet

And adding an initial command to spin up a faucet server independently

ignite faucet serve [account] [--port ...] [--rpc ...]

• The command takes an account name from ignite account list When the user wants to bootstrap the faucet, they must first add the account they used with ignite account add ...
• The port is 4500 by default.
• Rpc is the rpc endpoint of the chain and would be http://0.0.0.0:26657 by default

I'm also suggesting to move

ignite chain faucet

to

ignite faucet request

To make this command more explicit and as it could be used for a faucet not bootstrapped with the serve command

Later, ignite faucet could be extended, allow more advanced option like spinning up a webapp that include a captcha or identity verification method for more advanced and production faucet

ignite faucet webapp

[fadeev]

I like this idea, because it makes the ignite binary more useful in production-like environments, and not only for local development. My only concern is people might not want to install a pretty big binary for things like faucets.