-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added a new example that seamlessly works across 2 different machines. #84
base: main
Are you sure you want to change the base?
Conversation
This is a nice simple example. It's not a test per-se (as in we wouldn't run it as part of automated tests) Can you speak more to why you wanted this @nuttwork ? |
I agree with you about it being unsuitable for a test in the current form.
I looked at other modules such as ssb-minimal-pub-server, ssb-client-basic,
etc. and none have an example that works across machines, so I wrote one
up...
…On Mon, Mar 27, 2023 at 5:38 PM mix irving ***@***.***> wrote:
This is a nice simple example. It's not a test per-se (as in we wouldn't
run it as part of automated tests)
I wonder if it could be converted into a single file that behaves as a
test and whether that would be useful.
Can you speak more to why you wanted this @nuttwork
<https://github.com/nuttwork> ?
—
Reply to this email directly, view it on GitHub
<#84 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APR4L55RGSSQN4IT3N6GIFLW6IXJXANCNFSM6AAAAAAWB7JQUA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
If it's an example not a test, should we make a new |
README.md
Outdated
Added talk.js and listen.js that can run on 2 different machines. | ||
Usage: node listen.js | ||
Then copy the key it prints and the host IP on which you ran listen.js and put it in talk.js | ||
Usage: node talk.js |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the markdown here doesn't display well, e.g. https://github.com/nuttwork/secret-stack/blob/example/README.md
might be better written like:
See also: [`talk.js`](./examples/talk.js) and [`listen.js`](./examples/listen.js)
Where the rest of the documentation could be in those files.
I like @ahdinosaur suggestion of an examples folder. Lets do that. |
Changed markdown per suggestion from ahdinosaur.
These two files work together to form one example of how to communicate across machines.