├── .github
└── ISSUE_TEMPLATE
│ ├── bug_report.md
│ ├── feature_request.md
│ └── pull_request_template.md
├── .gitignore
├── CODE_OF_CONDUCT.md
├── CONTRIBUTING.md
├── LICENSE
├── README.md
├── SECURITY.md
├── client
├── .eslintrc.cjs
├── favicon.ico
├── index.html
├── package-lock.json
├── package.json
├── postcss.config.js
├── src
│ ├── App.css
│ ├── App.jsx
│ ├── assets
│ │ ├── exit-fullscreen-symbol.svg
│ │ ├── fullscreen-symbol.svg
│ │ └── keyboard-symbol.svg
│ ├── components
│ │ ├── Browser
│ │ │ ├── BrowserHome.jsx
│ │ │ ├── FileTransferer.jsx
│ │ │ └── Header.jsx
│ │ ├── Home.jsx
│ │ └── Mobile
│ │ │ ├── FileReceiver.jsx
│ │ │ ├── FileTransferer.jsx
│ │ │ ├── FullScreen.jsx
│ │ │ ├── Header.jsx
│ │ │ ├── Keyboard.jsx
│ │ │ ├── MobileHome.jsx
│ │ │ └── Touchpad.jsx
│ ├── index.css
│ ├── main.jsx
│ └── utils
│ │ ├── config.js
│ │ ├── file_transfer.js
│ │ ├── geo.js
│ │ └── webRTC_setter.js
├── tailwind.config.js
└── vite.config.js
├── server
├── package-lock.json
├── package.json
└── src
│ ├── index.js
│ ├── routers
│ └── touchpad.js
│ └── utils
│ ├── file_transfer.js
│ ├── get_ip.js
│ ├── global_calls.js
│ └── signaling_server.js
└── setup.sh
/.github/ISSUE_TEMPLATE/bug_report.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Bug report
3 | about: Create a report to help us improve
4 | title: ''
5 | labels: ''
6 | assignees: ''
7 |
8 | ---
9 |
10 | ### How Do I Submit a Good Bug Report?
11 |
12 | To help us address your issue effectively, please provide the following details when submitting a bug report:
13 |
14 | **Describe the Bug**
15 | Provide a clear and concise description of what the bug is.
16 |
17 | **To Reproduce**
18 | Steps to reproduce the behavior:
19 | 1. Go to '...'
20 | 2. Click on '....'
21 | 3. Scroll down to '....'
22 | 4. See error
23 |
24 | **Expected Behavior**
25 | Describe what you expected to happen in a clear and concise manner.
26 |
27 | **Screenshots**
28 | If applicable, add screenshots to help explain your problem.
29 |
30 | **Desktop (please complete the following information):**
31 | - OS: [e.g., Windows, macOS, Linux]
32 | - Browser: [e.g., Chrome, Firefox, Safari]
33 | - Version: [e.g., 22]
34 |
35 | **Smartphone (please complete the following information):**
36 | - Device: [e.g., iPhone 12, Samsung Galaxy S21]
37 | - OS: [e.g., iOS 14.4, Android 11]
38 | - Browser: [e.g., Safari, Chrome, stock browser]
39 | - Version: [e.g., 22]
40 |
41 | **Additional Context**
42 | Add any other context about the problem here. This can include logs, error messages, or any other relevant information.
43 |
44 | Once you've gathered this information, please open an [Issue](https://github.com/Bhavye2003Developer/remotely/issues/new) and provide all the details listed above. This will help us diagnose and fix the issue as quickly as possible. Thank you for helping us improve Remotely!
45 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/feature_request.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Feature request
3 | about: Suggest an idea for this project
4 | title: ''
5 | labels: ''
6 | assignees: ''
7 |
8 | ---
9 |
10 | ### How Do I Submit a Good Enhancement Suggestion?
11 |
12 | To help us understand and consider your feature request effectively, please provide the following details:
13 |
14 | **Is your feature request related to a problem? Please describe.**
15 | Provide a clear and concise description of what the problem is. Example: "I'm always frustrated when [...]"
16 |
17 | **Describe the Solution You'd Like**
18 | Clearly describe what you want to happen. Explain how this solution would solve the problem or improve the project.
19 |
20 | **Describe Alternatives You've Considered**
21 | List any alternative solutions or features you've considered and why you believe they might not be as effective.
22 |
23 | **Additional Context**
24 | Add any other context or screenshots about the feature request here. This can include use cases, potential benefits, or any other relevant information.
25 |
26 | Once you've gathered this information, please open an [Issue](https://github.com/Bhavye2003Developer/remotely/issues/new) and provide all the details listed above. This will help us evaluate and implement the feature as quickly as possible. Thank you for helping us improve Remotely!
27 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/pull_request_template.md:
--------------------------------------------------------------------------------
1 | # Pull Request Template
2 |
3 | ## Description
4 |
5 | Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
6 |
7 | Fixes # (issue)
8 |
9 | ## Type of Change
10 |
11 | Please delete options that are not relevant.
12 |
13 | - [ ] Bug fix (non-breaking change which fixes an issue)
14 | - [ ] New feature (non-breaking change which adds functionality)
15 | - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
16 | - [ ] Documentation update
17 |
18 | ## How Has This Been Tested?
19 |
20 | Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.
21 |
22 | - [ ] Test A
23 | - [ ] Test B
24 |
25 | **Test Configuration**:
26 | * Firmware version:
27 | * Hardware:
28 | * Toolchain:
29 | * SDK:
30 |
31 | ## Checklist:
32 |
33 | - [ ] My code follows the style guidelines of this project
34 | - [ ] I have performed a self-review of my own code
35 | - [ ] I have commented my code, particularly in hard-to-understand areas
36 | - [ ] I have made corresponding changes to the documentation
37 | - [ ] My changes generate no new warnings
38 | - [ ] I have added tests that prove my fix is effective or that my feature works
39 | - [ ] New and existing unit tests pass locally with my changes
40 | - [ ] Any dependent changes have been merged and published in downstream modules
41 |
42 | ## Screenshots (if applicable):
43 |
44 | Please add any screenshots that can help illustrate the changes made in this pull request.
45 |
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | # Logs
2 | logs
3 | *.log
4 | npm-debug.log*
5 | yarn-debug.log*
6 | yarn-error.log*
7 | pnpm-debug.log*
8 | lerna-debug.log*
9 |
10 | node_modules
11 | dist
12 | dist-ssr
13 | *.local
14 |
15 | # Editor directories and files
16 | .vscode/*
17 | !.vscode/extensions.json
18 | .idea
19 | .DS_Store
20 | *.suo
21 | *.ntvs*
22 | *.njsproj
23 | *.sln
24 | *.sw?
25 |
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 | # Contributor Covenant Code of Conduct
2 |
3 | ## Our Pledge
4 |
5 | We as members, contributors, and leaders pledge to make participation in our
6 | community a harassment-free experience for everyone, regardless of age, body
7 | size, visible or invisible disability, ethnicity, sex characteristics, gender
8 | identity and expression, level of experience, education, socio-economic status,
9 | nationality, personal appearance, race, religion, or sexual identity
10 | and orientation.
11 |
12 | We pledge to act and interact in ways that contribute to an open, welcoming,
13 | diverse, inclusive, and healthy community.
14 |
15 | ## Our Standards
16 |
17 | Examples of behavior that contributes to a positive environment for our
18 | community include:
19 |
20 | * Demonstrating empathy and kindness toward other people
21 | * Being respectful of differing opinions, viewpoints, and experiences
22 | * Giving and gracefully accepting constructive feedback
23 | * Accepting responsibility and apologizing to those affected by our mistakes,
24 | and learning from the experience
25 | * Focusing on what is best not just for us as individuals, but for the
26 | overall community
27 |
28 | Examples of unacceptable behavior include:
29 |
30 | * The use of sexualized language or imagery, and sexual attention or
31 | advances of any kind
32 | * Trolling, insulting or derogatory comments, and personal or political attacks
33 | * Public or private harassment
34 | * Publishing others' private information, such as a physical or email
35 | address, without their explicit permission
36 | * Other conduct which could reasonably be considered inappropriate in a
37 | professional setting
38 |
39 | ## Enforcement Responsibilities
40 |
41 | Community leaders are responsible for clarifying and enforcing our standards of
42 | acceptable behavior and will take appropriate and fair corrective action in
43 | response to any behavior that they deem inappropriate, threatening, offensive,
44 | or harmful.
45 |
46 | Community leaders have the right and responsibility to remove, edit, or reject
47 | comments, commits, code, wiki edits, issues, and other contributions that are
48 | not aligned to this Code of Conduct, and will communicate reasons for moderation
49 | decisions when appropriate.
50 |
51 | ## Scope
52 |
53 | This Code of Conduct applies within all community spaces, and also applies when
54 | an individual is officially representing the community in public spaces.
55 | Examples of representing our community include using an official e-mail address,
56 | posting via an official social media account, or acting as an appointed
57 | representative at an online or offline event.
58 |
59 | ## Enforcement
60 |
61 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
62 | reported to the community leaders responsible for enforcement at
63 | bhavyedevelopment2003@gmail.com.
64 | All complaints will be reviewed and investigated promptly and fairly.
65 |
66 | All community leaders are obligated to respect the privacy and security of the
67 | reporter of any incident.
68 |
69 | ## Enforcement Guidelines
70 |
71 | Community leaders will follow these Community Impact Guidelines in determining
72 | the consequences for any action they deem in violation of this Code of Conduct:
73 |
74 | ### 1. Correction
75 |
76 | **Community Impact**: Use of inappropriate language or other behavior deemed
77 | unprofessional or unwelcome in the community.
78 |
79 | **Consequence**: A private, written warning from community leaders, providing
80 | clarity around the nature of the violation and an explanation of why the
81 | behavior was inappropriate. A public apology may be requested.
82 |
83 | ### 2. Warning
84 |
85 | **Community Impact**: A violation through a single incident or series
86 | of actions.
87 |
88 | **Consequence**: A warning with consequences for continued behavior. No
89 | interaction with the people involved, including unsolicited interaction with
90 | those enforcing the Code of Conduct, for a specified period of time. This
91 | includes avoiding interactions in community spaces as well as external channels
92 | like social media. Violating these terms may lead to a temporary or
93 | permanent ban.
94 |
95 | ### 3. Temporary Ban
96 |
97 | **Community Impact**: A serious violation of community standards, including
98 | sustained inappropriate behavior.
99 |
100 | **Consequence**: A temporary ban from any sort of interaction or public
101 | communication with the community for a specified period of time. No public or
102 | private interaction with the people involved, including unsolicited interaction
103 | with those enforcing the Code of Conduct, is allowed during this period.
104 | Violating these terms may lead to a permanent ban.
105 |
106 | ### 4. Permanent Ban
107 |
108 | **Community Impact**: Demonstrating a pattern of violation of community
109 | standards, including sustained inappropriate behavior, harassment of an
110 | individual, or aggression toward or disparagement of classes of individuals.
111 |
112 | **Consequence**: A permanent ban from any sort of public interaction within
113 | the community.
114 |
115 | ## Attribution
116 |
117 | This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118 | version 2.0, available at
119 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
120 |
121 | Community Impact Guidelines were inspired by [Mozilla's code of conduct
122 | enforcement ladder](https://github.com/mozilla/diversity).
123 |
124 | [homepage]: https://www.contributor-covenant.org
125 |
126 | For answers to common questions about this code of conduct, see the FAQ at
127 | https://www.contributor-covenant.org/faq. Translations are available at
128 | https://www.contributor-covenant.org/translations.
129 |
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | # Contributing to Remotely
2 |
3 | First off, thanks for taking the time to contribute!
4 |
5 | All types of contributions are encouraged and valued. See the [Table of Contents](#table-of-contents) for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions.
6 |
7 | > And if you like the project, but just don't have time to contribute, that's fine. There are other easy ways to support the project and show your appreciation, which we would also be very happy about:
8 | > - Star the project
9 | > - Tweet about it
10 | > - Refer this project in your project's readme
11 | > - Mention the project at local meetups and tell your friends/colleagues
12 |
13 | ## Table of Contents
14 |
15 | - [Code of Conduct](#code-of-conduct)
16 | - [I Have a Question](#i-have-a-question)
17 | - [I Want To Contribute](#i-want-to-contribute)
18 | - [Reporting Bugs](#reporting-bugs)
19 | - [Suggesting Enhancements](#suggesting-enhancements)
20 | - [Your First Code Contribution](#your-first-code-contribution)
21 | - [Improving The Documentation](#improving-the-documentation)
22 | - [Styleguides](#styleguides)
23 | - [Commit Messages](#commit-messages)
24 | - [Join The Project Team](#join-the-project-team)
25 | - [Attribution](#attribution)
26 |
27 | ## Code of Conduct
28 |
29 | This project and everyone participating in it is governed by the
30 | [Remotely Code of Conduct](blob/master/CODE_OF_CONDUCT.md).
31 | By participating, you are expected to uphold this code. Please report unacceptable behavior
32 | to [bhavyedevelopment2003@gmail.com](mailto:bhavyedevelopment2003@gmail.com).
33 |
34 | ## I Have a Question
35 |
36 | > If you want to ask a question, we assume that you have read the available [Documentation](https://github.com/Bhavye2003Developer/remotely#readme).
37 |
38 | Before you ask a question, it is best to search for existing [Issues](https://github.com/Bhavye2003Developer/remotely/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
39 |
40 | If you then still feel the need to ask a question and need clarification, we recommend the following:
41 |
42 | - Open an [Issue](https://github.com/Bhavye2003Developer/remotely/issues/new).
43 | - Provide as much context as you can about what you're running into.
44 | - Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.
45 |
46 | We will then take care of the issue as soon as possible.
47 |
48 | ## I Want To Contribute
49 |
50 | > ### Legal Notice
51 | > When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content and that the content you contribute may be provided under the project license.
52 |
53 | ### Reporting Bugs
54 |
55 | #### Before Submitting a Bug Report
56 |
57 | A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.
58 |
59 | - Make sure that you are using the latest version.
60 | - Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://github.com/Bhavye2003Developer/remotely#readme). If you are looking for support, you might want to check [this section](#i-have-a-question)).
61 | - To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/Bhavye2003Developer/remotely/issues?q=label%3Abug).
62 | - Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have discussed the issue.
63 | - Collect information about the bug:
64 | - Stack trace (Traceback)
65 | - OS, Platform and Version (Windows, Linux, macOS, x86, ARM)
66 | - Version of the interpreter, compiler, SDK, runtime environment, package manager, depending on what seems relevant.
67 | - Possibly your input and the output
68 | - Can you reliably reproduce the issue? And can you also reproduce it with older versions?
69 |
70 | #### How Do I Submit a Good Bug Report?
71 |
72 | > You must never report security related issues, vulnerabilities or bugs including sensitive information to the issue tracker, or elsewhere in public. Instead sensitive bugs must be sent by email to [bhavyedevelopment2003@gmail.com](mailto:bhavyedevelopment2003@gmail.com).
73 |
74 | We use GitHub issues to track bugs and errors. If you run into an issue with the project:
75 |
76 | - Open an [Issue](https://github.com/Bhavye2003Developer/remotely/issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
77 | - Explain the behavior you would expect and the actual behavior.
78 | - Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case.
79 | - Provide the information you collected in the previous section.
80 |
81 | Once it's filed:
82 |
83 | - The project team will label the issue accordingly.
84 | - A team member will try to reproduce the issue with your provided steps. If there are no reproduction steps or no obvious way to reproduce the issue, the team will ask you for those steps and mark the issue as `needs-repro`. Bugs with the `needs-repro` tag will not be addressed until they are reproduced.
85 | - If the team is able to reproduce the issue, it will be marked `needs-fix`, as well as possibly other tags (such as `critical`), and the issue will be left to be [implemented by someone](#your-first-code-contribution).
86 |
87 | ### Suggesting Enhancements
88 |
89 | This section guides you through submitting an enhancement suggestion for Remotely, **including completely new features and minor improvements to existing functionality**. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions.
90 |
91 | #### Before Submitting an Enhancement
92 |
93 | - Make sure that you are using the latest version.
94 | - Read the [documentation](https://github.com/Bhavye2003Developer/remotely#readme) carefully and find out if the functionality is already covered, maybe by an individual configuration.
95 | - Perform a [search](https://github.com/Bhavye2003Developer/remotely/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
96 | - Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.
97 |
98 | #### How Do I Submit a Good Enhancement Suggestion?
99 |
100 | Enhancement suggestions are tracked as [GitHub issues](https://github.com/Bhavye2003Developer/remotely/issues).
101 |
102 | - Use a **clear and descriptive title** for the issue to identify the suggestion.
103 | - Provide a **step-by-step description of the suggested enhancement** in as many details as possible.
104 | - **Describe the current behavior** and **explain which behavior you expected to see instead** and why. At this point you can also tell which alternatives do not work for you.
105 | - You may want to **include screenshots and animated GIFs** which help you demonstrate the steps or point out the part which the suggestion is related to. You can use [this tool](https://www.cockos.com/licecap/) to record GIFs on macOS and Windows, and [this tool](https://github.com/colinkeenan/silentcast) or [this tool](https://github.com/GNOME/byzanz) on Linux.
106 | - **Explain why this enhancement would be useful** to most Remotely users. You may also want to point out the other projects that solved it better and which could serve as inspiration.
107 |
108 | ### Your First Code Contribution
109 |
110 | TBD
111 |
112 | ### Improving The Documentation
113 |
114 | TBD
115 |
116 | ## Styleguides
117 |
118 | ### Commit Messages
119 |
120 | TBD
121 |
122 | ## Join The Project Team
123 |
124 | TBD
125 |
126 | ## Attribution
127 |
128 | This guide is based on the **contributing.md**. [Make your own](https://contributing.md/)!
129 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | MIT License
2 |
3 | Copyright (c) 2024 Bhavye2003Developer
4 |
5 | Permission is hereby granted, free of charge, to any person obtaining a copy
6 | of this software and associated documentation files (the "Software"), to deal
7 | in the Software without restriction, including without limitation the rights
8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9 | copies of the Software, and to permit persons to whom the Software is
10 | furnished to do so, subject to the following conditions:
11 |
12 | The above copyright notice and this permission notice shall be included in all
13 | copies or substantial portions of the Software.
14 |
15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21 | SOFTWARE.
22 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # Remotely
2 |
3 | ## Overview
4 |
5 | Remotely is a versatile application that transforms your mobile device into a powerful remote control for your desktop. This application offers multiple functionalities, including file transfers, touchpad, and keyboard features, making it an essential tool for seamless interaction between your mobile and desktop environments.
6 |
7 | ## Features
8 |
9 | 1. **Multiple File Transfer from Mobile to Desktop:**
10 |
11 | - Easily transfer multiple files from your mobile device to your desktop.
12 |
13 | 2. **Single File Transfer from Desktop to Mobile:**
14 |
15 | - Transfer a single file from your desktop to your mobile device with ease.
16 |
17 | 3. **Touchpad:**
18 |
19 | - Use your mobile device as a touchpad to control the cursor on your desktop.
20 |
21 | - Supports coordinate transfer to enable smooth cursor movements.
22 |
23 | 4. **Keyboard:**
24 |
25 | - Use your mobile device as a keyboard to type on your desktop.
26 |
27 | - Enhances productivity with remote typing capabilities.
28 |
29 | ## Technologies Used
30 |
31 | 1. **Backend:**
32 |
33 | - **Node.js:** A powerful JavaScript runtime for building the backend of the application.
34 |
35 | 2. **Frontend:**
36 |
37 | - **React:** A popular JavaScript library for building user interfaces.
38 |
39 | - **Tailwind CSS:** A utility-first CSS framework for styling the frontend.
40 |
41 | 3. **Communication:**
42 |
43 | - **WebSockets:** Used for real-time communication between the touchpad and the desktop to transfer coordinates for cursor movements.
44 |
45 | - **WebRTC:** Used for peer-to-peer file transfer between the desktop and mobile device, ensuring fast and secure data transfer.
46 |
47 | ## Setup and Installation
48 |
49 | ### Prerequisites
50 |
51 | - Node.js installed on your system.
52 |
53 | - npm (Node Package Manager) installed.
54 |
55 | - A modern web browser (e.g., Chrome, Firefox).
56 |
57 | ### Quick Setup
58 |
59 | 1. Clone the repository:
60 |
61 | ```bash
62 |
63 | git clone https://github.com/Bhavye2003Developer/remotely.git
64 |
65 | ```
66 |
67 | 2. Change to the Project Directory
68 |
69 | ```bash
70 |
71 | cd remotely
72 |
73 | ```
74 |
75 | 3. Run the script
76 |
77 | ```bash
78 | ./setup.sh
79 | ```
80 |
81 | This script will automatically install all dependencies required for the project.
82 |
83 | ### Launch the Application
84 |
85 | - After successfully running the setup script, follow the instructions displayed in the terminal to access the application.
86 | - Typically, you will need to visit the IP address shown on the terminal from your mobile device to begin using Desktop Remote.
87 |
88 | ## License
89 |
90 | This project is licensed under the MIT License - see the LICENSE file for details.
91 |
--------------------------------------------------------------------------------
/SECURITY.md:
--------------------------------------------------------------------------------
1 | # Security Policy
2 |
3 | ## Supported Versions
4 |
5 | The following versions of the Remotely project are currently being supported with security updates:
6 |
7 | | Version | Supported |
8 | | ------- | ------------------ |
9 | | 1.2.x | :white_check_mark: |
10 | | 1.1.x | :white_check_mark: |
11 | | 1.0.x | :x: |
12 | | < 1.0 | :x: |
13 |
14 | ## Reporting a Vulnerability
15 |
16 | If you discover a vulnerability in the Remotely project, please follow these steps to report it:
17 |
18 | 1. **Email the vulnerability details to:** [bhavyedevelopment2003@gmail.com](mailto:bhavyedevelopment2003@gmail.com).
19 | 2. **Include the following information:**
20 | - A detailed description of the vulnerability.
21 | - Steps to reproduce the vulnerability.
22 | - Any potential impacts of the vulnerability.
23 | - Any possible fixes you may have.
24 |
25 | You can expect an update on your reported vulnerability within 72 hours of submission.
26 |
27 | ### What to Expect After Reporting
28 |
29 | - **Acknowledgement:** We will acknowledge receipt of your report within 24 hours.
30 | - **Investigation:** We will investigate the vulnerability and verify its validity.
31 | - **Fixing the Issue:** If the vulnerability is confirmed, we will work on a fix and update you on the progress.
32 | - **Update:** We will provide regular updates (at least once a week) on the status of the fix.
33 | - **Resolution:** Once the vulnerability is fixed, we will notify you and give you credit for the discovery, if desired.
34 |
35 | Thank you for helping to keep Remotely secure!
36 |
--------------------------------------------------------------------------------
/client/.eslintrc.cjs:
--------------------------------------------------------------------------------
1 | module.exports = {
2 | root: true,
3 | env: { browser: true, es2020: true },
4 | extends: [
5 | 'eslint:recommended',
6 | 'plugin:react/recommended',
7 | 'plugin:react/jsx-runtime',
8 | 'plugin:react-hooks/recommended',
9 | ],
10 | ignorePatterns: ['dist', '.eslintrc.cjs'],
11 | parserOptions: { ecmaVersion: 'latest', sourceType: 'module' },
12 | settings: { react: { version: '18.2' } },
13 | plugins: ['react-refresh'],
14 | rules: {
15 | 'react/jsx-no-target-blank': 'off',
16 | 'react-refresh/only-export-components': [
17 | 'warn',
18 | { allowConstantExport: true },
19 | ],
20 | },
21 | }
22 |
--------------------------------------------------------------------------------
/client/favicon.ico:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Bhavye2003Developer/remotely/a1583ef32ed279848f3b8d119d97bccf71af1064/client/favicon.ico
--------------------------------------------------------------------------------
/client/index.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
10 | Remotely
11 |
12 |
13 |
14 |
15 |
16 |
17 |
--------------------------------------------------------------------------------
/client/package.json:
--------------------------------------------------------------------------------
1 | {
2 | "name": "client",
3 | "private": true,
4 | "version": "0.0.0",
5 | "type": "module",
6 | "scripts": {
7 | "dev": "vite",
8 | "build": "vite build",
9 | "lint": "eslint . --ext js,jsx --report-unused-disable-directives --max-warnings 0",
10 | "preview": "vite preview"
11 | },
12 | "dependencies": {
13 | "axios": "^1.7.2",
14 | "react": "^18.2.0",
15 | "react-device-detect": "^2.2.3",
16 | "react-dom": "^18.2.0",
17 | "react-router-dom": "^6.23.1",
18 | "react-toastify": "^10.0.5",
19 | "vite-plugin-svgr": "^4.2.0"
20 | },
21 | "devDependencies": {
22 | "@types/react": "^18.2.66",
23 | "@types/react-dom": "^18.2.22",
24 | "@vitejs/plugin-react": "^4.2.1",
25 | "autoprefixer": "^10.4.19",
26 | "eslint": "^8.57.0",
27 | "eslint-plugin-react": "^7.34.1",
28 | "eslint-plugin-react-hooks": "^4.6.0",
29 | "eslint-plugin-react-refresh": "^0.4.6",
30 | "postcss": "^8.4.38",
31 | "tailwindcss": "^3.4.4",
32 | "vite": "^5.2.0"
33 | }
34 | }
35 |
--------------------------------------------------------------------------------
/client/postcss.config.js:
--------------------------------------------------------------------------------
1 | export default {
2 | plugins: {
3 | tailwindcss: {},
4 | autoprefixer: {},
5 | },
6 | }
7 |
--------------------------------------------------------------------------------
/client/src/App.css:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Bhavye2003Developer/remotely/a1583ef32ed279848f3b8d119d97bccf71af1064/client/src/App.css
--------------------------------------------------------------------------------
/client/src/App.jsx:
--------------------------------------------------------------------------------
1 | import "./App.css";
2 | import Home from "./components/Home";
3 |
4 | const App = () => {
5 | return (
6 |
72 | {isConnectedToLocal
73 | ? "Ready to receive files. If not receiving, ensure the sender is active."
74 | : "Please open 'http://localhost:5173/send-file' on your desktop to start sending files."}
75 |