isle/go/daemon/children
Brian Picciano 8c3e6a2845 Separate Daemon and Network logic into separate packages
In a world where the daemon can manage more than one network, the Daemon
is really responsible only for knowing which networks are currently
joined, creating/joining/leaving networks, and routing incoming RPC
requests to the correct network handler as needed.

The new network package, with its Network interface, inherits most of
the logic that Daemon used to have, leaving Daemon only the parts needed
for the functionality just described. There's a lot of cleanup done here
in order to really nail down the separation of concerns between the two,
especially around directory creation.
2024-09-09 16:34:00 +02:00
..
children.go Separate Daemon and Network logic into separate packages 2024-09-09 16:34:00 +02:00
diff.go Factor daemon.Children into its own package 2024-09-07 15:46:59 +02:00
dnsmasq.go Factor daemon.Children into its own package 2024-09-07 15:46:59 +02:00
garage.go Factor daemon.Children into its own package 2024-09-07 15:46:59 +02:00
jigs.go Factor daemon.Children into its own package 2024-09-07 15:46:59 +02:00
nebula.go Factor daemon.Children into its own package 2024-09-07 15:46:59 +02:00
pmux.go Separate Daemon and Network logic into separate packages 2024-09-09 16:34:00 +02:00