fix(web): restore Settings → Community tab (self-host) + get-key form + redeem clarity#86
Merged
Merged
Conversation
…email form Reverts the tab removal (#85) for the PUBLIC/self-host build: on self-host the operator IS the user, and this tab is their only in-app path to enable publishing. Restores the nav entry, the page, and the CommunitySettings component, and adds a 'Get a free community key' email form — it posts to the hosted licensing service (PUBLIC_COMMUNITY_LICENSE_URL) which signs + emails a free community key the operator then sets as COMMUNITY_HUB_KEY. Browse/import needs no key and already works out of the box; this is only the publish-setup path. Cloud (private repo) intentionally does NOT carry this tab. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: nbkdoesntknowcoding <nischaybk@theboringpeople.in>
… for license redemption - RedeemLicense: the placeholder implied only the MNEMA-XXXX admin-code format, but community-license keys are long signed strings (the route accepts both). Neutral placeholder + copy that names both. - CommunitySettings: add a pointer clarifying that unlocking history/export is a separate per-workspace step done under Settings → Billing (vs the instance publish key here). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: nbkdoesntknowcoding <nischaybk@theboringpeople.in>
nbkdoesntknowcoding
changed the title
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.
Recovers the Settings → Community tab that #85 removed — public/self-host only — with a working get-a-key email form, plus two clarity fixes around the community-license flow.
Why
Removing the tab was right for multi-tenant cloud (users can't set instance env), but wrong for self-host: there, the operator is the user, and this tab is their only in-app path to enable publishing. (Cloud/private repo intentionally keeps it removed — deliberate open-core divergence.)
What
settings/community.astropage, and theCommunitySettingscomponent.PUBLIC_COMMUNITY_LICENSE_URL), which signs + emails a freecommunitykey the operator sets asCOMMUNITY_HUB_KEY. Shown only when publishing isn't configured.RedeemLicenseplaceholder implied only theMNEMA-XXXXadmin-code format, but community keys are long signed strings (the redeem route accepts both). Neutral placeholder + copy naming both.Boundary
Publish key = instance env (here). License redemption = per-workspace (Settings → Billing). Two uses of the same signed key — made legible.
Signed off for the DCO.