mRemoteNG / mRemoteNG/mRemoteNG
SQL multiuser support
Open
Nobody has claimed this yet.
1.8 (Fenix)
Needs implementation
- Dominant language
- C#
- Stars
- 11.1k
- Forks
- 1.6k
- Avg merge
- 16h 58m
- Merged PRs (30d)
- 55
Description
In our team we would like to share our remote connections. The SQL connection is a great feature therefore. But it is not possible to make changes, because there are overwritten on mRemoteNG exit.
Current Behavior
All connections are stored in the database if you quit mRemoteNG
Expected Behavior
- Store only changed connection in the database
- Load changes on other connected clients
Your Environment
- Version used: 1.76.19
- Operating System and version: Windows 10 1709 x64
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.
Research direction
The issue names no files, tests, or entry points. Start by locating the SQL connection persistence and exit-save paths, then determine how another client could load changes; done means unchanged connections are not overwritten and updates appear on other connected clients.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql
- Domain
- databases, desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100