Cardano Updates

Co-authored-by: Jonathan Knowles <[email protected]>

Co-authored-by: Jonathan Knowles <[email protected]>

Update 2020-06-29_14-34-14_wallet-en.md

Update 2020-05-05_16-22-27_running-the-node-on-an-aws-instance-en.md

Update 2020-05-05_16-18-17_running-a-node-as-a-relay-en.md

Three changes that the hydra eval faster.  In order of importance:

1) Split `native` jobs into `linux` and `darwin`

Reduces the number of times hydra restarts the eval process because
memory is running low.  When both linux and darwin versions are
in the same attribute the evaluation runs out of memory more often
as it alternates between evaluating linux and darwin jobs.

Grouping all the linux and darwin jobs together reduces the number
of times the memory limit is reached.  This is makes the
"no change" eval more than 4x faster (270s vs 1300s).

2) Avoid duplicate `cabal configure`

To get a list of package names in the project we call
`cabalProject`, before using those names to provide the
overrides for another call to `cabalProject`.
`cabalProjectLocal` is not the same for the two calls and
as a result `cabal configure` is run twice (and it is very
slow for this project.  Passing the same `cabalProjectLocal`
value to both calls should improve evaluation greatly
when changes are made to the `cabal.project` or `.cabal`
files.

3) Include jobs to pin plan-nix

Pinning the `plan-nix` output means it is copied to the
hydra cache.  This may not improve eval on the hydra
machine itself, it will make testing evaluation on
other machines faster (since they will have access to the
cached plans).

It’s not possible to useEffect in combination with a ref object that should come from a component inside a render function:
https://medium.com/@teh_builder/ref-objects-inside-useeffect-hooks-eb7c15198780