Repository navigation
chore: connect Xperience's own Content Sync in the two-instance rig - #6
Merged
Merged
Conversation
The local rig could compare inventories but never run a real sync, so the end-to-end flow (missing, then sync, then in sync) and Kentico's handling of unpublished pages were unverified. - Bind ContentSynchronizationOptions from configuration in the DancingGoat example, so Content Sync is enabled per instance through environment variables and stays off otherwise - Document the setup in Contributing-Setup: trusting the development certificate, the target's HTTPS address, and the settings for both instances - Record the verified result in the foundation spec: syncing an unpublished page creates it unpublished on the target, and the status page follows each step - Ignore the sync packages Content Sync writes under the example's assets folder
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.
Connects Xperience's built-in Content Sync between the two local test instances, so a real sync can be checked end to end. No library code changes.
Changes
examples/DancingGoat/Program.csbindsContentSynchronizationOptionsfrom theContentSynchronizationconfiguration section. Content Sync is enabled per instance through environment variables and stays off otherwise.docs/Contributing-Setup.mdhas a new Connecting Xperience's own Content Sync section: trusting the .NET development certificate (Kentico requires the target on HTTPS with a trusted certificate), giving the target an HTTPS address, the settings for both instances, and how to run and check a sync..gitignore: ignoresexamples/DancingGoat/assets/synchronizations/, where Content Sync writes its packages.Verified (31.7.2, real Content Sync, target on
https://localhost:27311)/Articles/Clone_On_Roastson the sourceThis confirms Kentico's documented behavior for unpublished pages, and is the first check of the full missing → sync → in sync flow. The same setup can be used for the 30.8.0 two-instance release check.