[docs] Update dashboard persistence docs for flattened directory layout - #1657
Draft
aspire-repo-bot[bot] wants to merge 1 commit into
Draft
aspire-repo-bot[bot] wants to merge 1 commit into
aspire-repo-bot[bot] wants to merge 1 commit into
Conversation
Reflects the flattened storage layout from microsoft/aspire#20006: run snapshots now live directly under a shared runs directory (with an application storage-key marker file for discovery), and Resume-mode databases live under a shared resumes directory. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
aspire-repo-bot
Bot
added
the
docs-from-code
14 tasks
Contributor
Author
Frontend HTML artifact readyThe latest frontend build uploaded the This comment updates automatically when a new frontend build artifact is uploaded. |
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
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.
Documents changes from microsoft/aspire#20006
@JamesNKTargeting
release/13.6based on the source PR milestone13.6.Why
microsoft/aspire#20006 flattens the dashboard's on-disk persistence layout:
Runmode now stores all run snapshots directly under a sharedrunsdirectory (adding an empty marker file named with the application's storage key to each run directory so discovery can reject unrelated applications before readingrun.json), andResumemode now stores databases and lock files under a sharedresumesdirectory. Previously both modes nested data under a per-application directory. The dashboard docs described the old per-application-directory layout, so they needed updating to match.What changed
src/frontend/src/content/docs/dashboard/data-persistence.mdx: Updated the "Storage layout" section'sRunandResumemodeFileTreediagrams to show the new flattenedruns/andresumes/directories, described the new application storage-key marker file used for discovery, and updated the "Protect persisted data" section's permissions description to reference the sharedruns/resumesdirectories instead of a per-application directory.src/frontend/src/content/docs/dashboard/security-considerations.mdx: Updated the "Protect persisted data" section's Unix permissions bullet to match the new shared-directory layout, and reworded "Application-name partitioning" to "Application-name scoping" for accuracy.No new pages were created; both existing pages were updated in place.