sillsdev / sillsdev/langtechdepot
langtechdepot-subscribe.ps1 no longer needed?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 2
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 2
Description
@dhigby , When I run setup-langtechdepot.ps1, I can subscribe to folders along the way.
When I run langtechdepot-subscribe.ps1 it shows me what I have subscribed to, and any new or other folders I could subscribe to. Then for any folder I would like to subscribe to I need to type its name exactly.
I wonder if it would be easier for Windows users for us to provide a shortcut to open the default web browser to
http://127.0.0.1:8384/
Or in the original design phase, did you think you wanted to hide the complications and options that people could set wrongly if they see the interface to SyncThing?
If you would rather people used langtechdepot-subscribe than the SyncThing interface, it would be helpful if langtechdepot-subscribe.ps1 numbered the folders I could subscribe to, and then I would just type the number.
If you would like people to use the SyncThing interface, then I don't think we need langtechdepot-subscribe.ps1.
If you do want people to use langtechdepot-subscribe.ps1, then it will need a runner batch file. I have adapted the one that you made for the setup script and made it call the subscribe script and added it to the repo.
What do you think?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading langtechdepot-subscribe.ps1 and setup-langtechdepot.ps1, then compare the proposed runner batch file and the current Syncthing workflow. The maintainer must first choose whether users should use the script or the Syncthing interface; done means that choice and its resulting Windows user flow are clearly specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100