feat: configurable publish server URL#12520
Open
deephbz wants to merge 1 commit intologseq:masterfrom
Open
Conversation
Mirror the Custom Sync Server URL pattern (logseq#12459) for the single-page publish service. Settings -> Advanced -> Publish server URL opens a dialog that writes the URL to localStorage; frontend.config/publish-api-base reads it on each call so URL changes take effect without a restart. Unlike sync, publish does not need a push-config-to-worker step because the handler is purely HTTP request-response with no long-lived connection.
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.
Mirror the Custom Sync Server URL pattern (#12459) for the single-page publish service. Settings -> Advanced -> Publish server URL opens a dialog that writes the URL to localStorage; frontend.config/publish-api-base reads it on each call so URL changes take effect without a restart.
Unlike sync, publish does not need a push-config-to-worker step because the handler is purely HTTP request-response with no long-lived connection.
e.g.
