Ship a built-in default remote for the central server (LLP 0062)#233
Open
platypii wants to merge 1 commit into
Open
Ship a built-in default remote for the central server (LLP 0062)#233platypii wants to merge 1 commit into
platypii wants to merge 1 commit into
Conversation
Reaching the Hyparam-hosted central server took a `hyp remote add <url>` on every machine, and `query.default_remote` was validated but never consumed. - Ship a built-in `hyparam` target (https://hypaware.hyperparam.app), layered under the user's `query.remotes` so a same-named entry overrides it. - Make `--remote` optionally-valued: bare `--remote` resolves the default target (explicit `default_remote`, else the built-in); named `--remote <n>` is unchanged. Local-first stays: plain `hyp <verb>` still runs locally. - `hyp remote login` with no target resolves the same default. - Accept a built-in name for `query.default_remote` validation. - Record the design as LLP 0062, extending LLP 0033.
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.
Summary
Reaching the Hyparam-hosted central server took a
hyp remote add <url>on every machine, andquery.default_remotewas validated but never consumed. This ships the central server as a built-in target and wires the default so users never type the URL or a target name.hyparam → https://hypaware.hyperparam.app, layered under the user'squery.remotesso a same-named entry repoints or shadows it. The URL is non-secret and committable, exactly as ahyp remote addURL (LLP 0033 §targets).--remote:--remoteis now optionally-valued. Bare--remoteresolves the default target (explicitquery.default_remote, else the built-in); named--remote <name>is unchanged. Local-first stays intact: plainhyp <verb>still runs locally.hyp remote login: with no positional target, resolves the same default (companion of bare--remote).query.default_remotemay name a built-in, so a config can default to the central server without restating its URL.New user flow:
hyp remote login, thenhyp <verb> --remote.Design
Recorded as LLP 0062 (Decision), extending LLP 0033 §targets (which already anticipated bare
--remotein its schema comment). LLP 0033 gets anExtended-byforward-ref.Tests
--remoteparses to the default sentinel (verb-codec); bare--remoteroutes to the built-in central URL (verb-remote); bareremote loginresolves the default target (remote-login-command).npm run typecheckclean.Note
End users get this once it ships in a released
hypawarepackage; the deployed server is unaffected.