Commit Graph

10 Commits

Author SHA1 Message Date
6ec56f2a88 Pass NetworkConfig into Network loaders as an optional argument 2024-11-12 13:34:39 +01:00
04978fa9db Block for bucket list to sync across garage instances during init 2024-11-05 21:25:04 +01:00
5c41cedea3 Implement SetConfig, but in a stupid way 2024-10-24 19:52:08 +02:00
71bc182ab4 Implement initial go test for network.Create 2024-10-05 23:03:26 +02:00
31af39ce4c Embed default daemon.yml directly in entrypoint 2024-09-24 11:27:54 +02:00
6c036d1183 Check that two different networks aren't trying to use the same nebula port 2024-09-12 08:59:23 +02:00
df4eae8a5c Support configuring more than one network 2024-09-10 22:51:33 +02:00
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
86b2ba7bfa Factor daemon.Children into its own package 2024-09-07 15:46:59 +02:00
a840d0e701 Move common daemon types and values into daecommon 2024-09-07 15:11:04 +02:00