canton7/SyncTrayzor

Request (rather than issue) - more detailed docs

Open

#587 opened on Nov 23, 2020

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C# (5,477 stars) (390 forks)batch import
enhancementhelp wanted

Description

Under settings for SyncTrayzor there are advanced settings for a Syncthing path and home - should these be a path to the directory where Syncthing can be found or a full path that includes the exe?

As the default install on a system with syncthing already installed results in 3 copies of syncthing.exe across the system thats 2 to many and so being able to use syncthing from its own directory allows things to be clearned up a bit.

As a side note, while its been a long time since I've managed an environment that used the Windows Roaming feature and its possible that its usage may have changed, I was under the impression that moving .exe files around with it was considered a bad idea.

Contributor guide

Tech stack
csharp
Domain
desktopdocumentation
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic understanding of SyncTrayzorFamiliarity with Windows file paths
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
Investigate the settings page in the SyncTrayzor source code (likely in a .xaml or .cs file) to understand how the Syncthing path and home directory are used. Review existing documentation in the repository's README or wiki. Clarify whether the path should be the directory containing syncthing.exe or the full path including the executable. Update the documentation to remove ambiguity.