Sites and fixed devices keep their outbound paths

core/outbound_store.py keeps, in outbound.json, the sites of this computer
with their outbound paths in order, the active site, and the fixed devices
with their own paths. lookup() gives the fixed device's paths, else the
active site's, else none. The glossary gains outbound path, site, and fixed
device.

Refs: #35

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
This commit is contained in:
Jean-Pierre MartineauandClaude Haiku 5.5 committed 2026-11-07 13:06:08 -05:00
1 parent e2146f9092
commit c50656c586
5 files changed
+574

No files matched your search

+3
View File
@@ -183,6 +183,9 @@ and in quoted text.
| path | An ordered list of hops that you write or force (`a1,3d,…`) | |
| route | The sequence of nodes that a trace went through or will go through | |
| hop | One node in a path or a route | |
| outbound path | A path that starts at our node and goes out into the mesh, one or more hops long. The user trusts it for the first hops of a route, because the user knows which way out works | outbound leg (for this: an outbound leg is the outbound half of a trace) |
| site | A name for where the user takes the computer (`Home`, `Foulab`), with its outbound paths in order. One site is active | profile (for this: a profile is a connection alias in `config.toml`) |
| fixed device | A companion that never moves. It keeps its own outbound paths, and the active site does not apply to it | |
| via | The prefix for the relay chain of a packet or a message | |
| location | The coordinates (latitude and longitude) that a node advertises | coordinates (alone) |
| place | The named area nearest the location of a node: a neighbourhood, a village, a town, or a peak. It has a fine part and a coarse part (`Villeray, Montréal`) | location name, locality |