Document harper-config.yaml backup behavior#487
Merged
Conversation
Adds a "Configuration File Backups" section to the configuration
overview describing when Harper writes timestamped copies of
harper-config.yaml to {rootPath}/backup/, so the behavior is
discoverable via doc search.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
🚀 Preview DeploymentYour preview deployment is ready! 🔗 Preview URL: https://preview.harper-documentation.harperfabric.com/pr-487 This preview will update automatically when you push new commits. |
cb1kenobi
approved these changes
May 6, 2026
🧹 Preview CleanupThe preview deployment for this PR has been removed. |
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
2 participants
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
reference/configuration/overview.mddescribing when Harper writes timestamped copies ofharper-config.yamlto{rootPath}/backup/.harper/static/README.md(the default install landing page), which means it doesn't surface in doc-site search.set_configurationand CLI/env-var startup args), file location and naming convention (<ISO-timestamp>-harper-config.yaml.bak), the carve-out that direct YAML edits andHARPER_SET_CONFIG/HARPER_DEFAULT_CONFIGdo not produce timestamped backups, no rotation, and silent-on-failure behavior.Cross-links to the existing State Tracking section so readers see how the same
backup/folder is also used by the env-var configuration mechanism.Test plan
reference/configuration/overview.mdlocally and confirm the new section appears between Setting Configuration Values and Custom Config File Path.#state-trackingresolves.🤖 Generated with Claude Code