Wirebone coordinator - #5
Merged
Merged
Conversation
One DuckDB process can serve the Tailscale control plane and join as a tsnet client, persisting nodes and preauth keys in local tables or an attached DuckLake catalog.
Collapse the Wirebone SQL names into a hub vs tailscale_up convention, persist state in the quackscale schema, and add a PR smoke that embeds public wirebone.cpp.
DuckDB's default renderer ends with a bottom rule, so tail -1 was never true or false.
tsnet ignores SIGTERM and wait on the sleep|duckdb pipeline left the Action running after success.
The README now starts a fleet server with quackscale_hub and joins clients via tailscale_up; Tailscale and Headscale stay as alternatives.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.