livebook-dev/livebook
1
1
Fork 0
mirror of https://github.com/livebook-dev/livebook.git synced 2025-10-27 05:47:05 +08:00
Code Issues Projects Releases Packages Wiki Activity

Remove outdated steps in distributed portal example

Browse source
This commit is contained in:
José Valim 2022-04-16 18:02:58 +02:00 • committed by GitHub
parent 8b63332036
commit 78b9a11d8c
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
lib/livebook/notebook/explore/distributed_portals_with_elixir.livemd
View file

@ -701,6 +701,7 @@ and execute it:
```elixir
IO.inspect node()
IO.inspect Node.get_cookie()
:ok
```
Now paste the result of the other node name and its cookie in the variables below:
@ -717,20 +718,9 @@ Node.set_cookie(other_node, other_cookie)
Node.connect(other_node)
```
If it returns true, it means it connected as expected. The code above uses
`IO.gets/1` to read the input values, as we did earlier in this notebook,
then removes the trailing newline, and converts the strings to atoms. We
did so using the pipe operator `|>`, which gets the result of the previous
function and passes it as first argument to the next function. For example,
the first line is equivalent to `String.to_atom(String.trim(IO.gets("Other node: ")))`,
but it is much more readable as a pipeline.
Notice we also stored the name of the other node in a `other_node` variable
for convenience.
Now we are ready to start a distributed transfer. The first step is to go
to the other notebook and shoot a door. You can try calling the following
there:
If it returns true, it means it connected as expected and we are ready to start a
distributed transfer. The first step is to go to the other notebook and shoot a door.
You can try calling the following there:
<!-- livebook:{"force_markdown":true} -->