Run a robust faucet and document the usage

[schemar]

This is a follow-up ticket to #12.

#12 already created all necessary keys, funded them, and started the faucet to run with the new chains
(@gulshanvasnani please confirm).

Tasks in this issue:

• Run the faucet in a way where it automatically restarts whenever the process crashes.
• Document privately for OST how to use the faucet (especially address and port).

[schemar]

@gulshanvasnani can you please confirm the assumptions above?

[schemar]

First, I had to fix the linting setup. See #17.

[schemar]

I am working on figuring out the right ports. Comparing with the nodes machine.

[schemar]

@benjaminbollen your nodes server does not have enough memory to run nodes for four chains (3, 1406, 1407, 1414). How to proceed?

[schemar]

Do you want to increase the node or should we run fewer chains on this one?

[benjaminbollen]

let's only run testnet nodes, so excluding 1414 already

[schemar]

In order for the faucet to automatically restart, there must be an option to run it non-interactively. It requires hidden input of multiple passwords (one per faucet), which must become non-interactive.

[schemar]

The faucet is documented here: https://hackmd.io/WIzt8cufQXG2JsMEmY6lYA

[schemar]

If you pick this up for review, please check the documentation link: https://hackmd.io/WIzt8cufQXG2JsMEmY6lYA
You may also check how the faucet is running on the server in tmux. I created a script endless.sh which restarts the faucet whenever it crashes.

[gulshanvasnani]

I liked the endless.sh script to restart the faucet.
I tried the faucet for all the 3 chainId's. The error is error: could not fill address. Could you also check whether wiring for port forwarding is correct.

[0xsarvesh]

Documentation LGTM ✅
I couldn't review other things due to lack of access to the server.

[schemar]

I liked the endless.sh script to restart the faucet.
I tried the faucet for all the 3 chainId's. The error is error: could not fill address. Could you also check whether wiring for port forwarding is correct.

That's weird, it worked for me 🤔 I will check the server to see the error log.

[schemar]

Someone messed with the SSH connection on the faucet server inside tmux. I restarted it. Can you please try again @gulshanvasnani ?

[schemar]

Also added a warning to https://hackmd.io/WIzt8cufQXG2JsMEmY6lYA

[deepesh-kn]

If you pick this up for review, please check the documentation link: https://hackmd.io/WIzt8cufQXG2JsMEmY6lYA

Documentation looks good 👍

You may also check how the faucet is running on the server in tmux. I created a script endless.sh which restarts the faucet whenever it crashes.

I was not able to find endless.sh. Can you point it to me?

[schemar]

ssh into faucet, then:

cd ./faucet
cat endless.sh

[pgev]

Robust implementation (+ detailed documentation) for the faucet is in place (the corresponding PR #17 is merged).

Closing this ticket: new tickets should be created for next improvements and bug fixes for the faucet.