This repository has been archived by the owner on Oct 1, 2020. It is now read-only.
actual different nodes are a helpful example case #31
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The original tutorial text is confusing for the primary reason that it doesn't actually talk about two separate nodes, but about two databases and two londiste workers running on the same machine. This does cover a lot of ground, but if one actually expects to replicate across multiple hosts, it's unclear where changes need to be made.
This revised text thusly has two major improvements:
(a) point to IP address, which is actually necessary esp for create-root, but in general.
(b) de-conflate the name of the database and worker, one of which would be the same on all nodes in the real world, and one of which must always be unique.
It would be possible to change this so that it points at 127.0.0.1, but that's still likely to leave some ambiguity, and I think it is easier for one who wants to test this on a single machine to translate from an example with actual addresses.