ssh sessions to multiple remote hosts with synced view
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- devtools
Research direction
No implementation files, tests, or entry points are identified in the issue. Start by reading issue #200524 about grouping remote hosts, then define the scope around grouped local and remote folders, difference handling, binary exclusions, test-gated syncing, and manual or automatic pushes.
Written by the indexing model from the issue text.
Description
I have a cluster of remote servers and I sometimes want to edit the same file on all servers. The current option is to edit the file locally and scp the local copy to each server. This is usually for files which are not committed to a git repository, such as environment files with sensitive data but it could also apply if I want to push the output of a frontend build to a set of servers.
It might be a cool feature if I can open a local folder and the same folder on a set of remote hosts and if they are all identical then show a single view so that an edit to one of the local files is copied automatically to all hosts in the set.
If there are any differences these could be highlighted in some way and click to compare as in the Source Control view. Binary files would be excluded from the diff check. A nice addition would be a flag that all tests must pass before the local file is copied to all remote hosts in the set and/or a button to push the changed file to the hosts in the set if auto sync is not enabled.
Issue #200524 discusses grouping remote hosts which would be useful for this feature.
The paths on the local host and the remote hosts may differ so in grouping the remote hosts a path to the remote folder could be defined for all hosts in the group.
- Dominant language
- TypeScript
- Stars
- 193k
- Forks
- 42.9k
- PR merge metrics
- PR metrics pending
Contributor guide
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.
More from microsoft/vscode
-
testplan-item
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
new release
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
testplan-item
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
testplan-item
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
All issues in microsoft/vscode
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·