-
Notifications
You must be signed in to change notification settings - Fork 8.1k
docs: added section on symlinks when using SFS #21712
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 2 commits
5422eb3
12d550a
34a5839
8a176f9
ecb462c
1e1f6b2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -80,6 +80,12 @@ | |
|
|
||
| In general, use your `.syncignore` file to exclude items that aren't critical to your workflow, especially those that would be slow to sync or use significant storage. | ||
|
|
||
| ## Symbolic links | ||
|
Check failure on line 83 in content/manuals/desktop/features/synchronized-file-sharing.md
|
||
|
|
||
| If your user does not have permissions to create symbolic links and your container attempts to create symbolic links in your file share instance, a **Problem** indicator with an `unable to create symbolic link` error will result. | ||
|
Check failure on line 85 in content/manuals/desktop/features/synchronized-file-sharing.md
|
||
chaomonica marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| See [Create symbolic links](https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-10/security/threat-protection/security-policy-settings/create-symbolic-links) for best practices and location of the "Create symbolic links" security policy setting. | ||
|
Check failure on line 87 in content/manuals/desktop/features/synchronized-file-sharing.md
|
||
chaomonica marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| ## Known issues | ||
|
|
||
| - Changes made to `.syncignore` don't lead to immediate deletions unless the file share is recreated. In other words, files that are newly ignored due to modifications in the `.syncignore` file remain in their current location, but are no longer updated during synchronization. | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of having a new section, I think it'd be better to have this as a bullet point in the 'Known issues' section below. WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@aevesdocker I will format this into a bullet point. Thank you for pointing this out!