github-starred/awesome-sunshine
2
0
Fork 0
mirror of https://github.com/LizardByte/awesome-sunshine.git synced 2026-07-17 07:22:34 -05:00
Code Issues 43 Packages Projects Releases Wiki Activity

[PR #68] [MERGED] docs: add vuinputd #455

New Issue
Closed
opened 2026-05-12 13:08:47 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-05-12 13:08:47 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/LizardByte/awesome-sunshine/pull/68
Author: @joleuger
Created: 12/19/2025
Status: ✅ Merged
Merged: 12/20/2025
Merged by: @ReenigneArcher

Base: master ← Head: master

📝 Commits (1)

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 README.md (+1 -0)

📄 Description

Description

Add entry of vuinputd as mentioned on https://github.com/LizardByte/Sunshine/issues/3768
vuinputd is a Linux daemon for creating and forwarding virtual input devices, designed for sandboxed or containerized Sunshine setups. Use "Enabling container-friendly input handling for Sunshine on Linux." as short description.

Screenshot

Issues Fixed or Closed

Roadmap Issues

Type of Change

  • feat: New feature (non-breaking change which adds functionality)
  • fix: Bug fix (non-breaking change which fixes an issue)
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semicolons, etc.)
  • refactor: Code change that neither fixes a bug nor adds a feature
  • perf: Code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies
  • ci: Changes to CI configuration files and scripts
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit
  • BREAKING CHANGE: Introduces a breaking change (can be combined with any type above)

Checklist

  • Code follows the style guidelines of this project
  • Code has been self-reviewed
  • Code has been commented, particularly in hard-to-understand areas
  • Code docstring/documentation-blocks for new or existing methods/components have been added or updated
  • Unit tests have been added or updated for any new or modified functionality

AI Usage

  • None: No AI tools were used in creating this PR
  • Light: AI provided minor assistance (formatting, simple suggestions)
  • Moderate: AI helped with code generation or debugging specific parts
  • Heavy: AI generated most or all of the code changes

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/LizardByte/awesome-sunshine/pull/68 **Author:** [@joleuger](https://github.com/joleuger) **Created:** 12/19/2025 **Status:** ✅ Merged **Merged:** 12/20/2025 **Merged by:** [@ReenigneArcher](https://github.com/ReenigneArcher) **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (1) - [`f08e5ea`](https://github.com/LizardByte/awesome-sunshine/commit/f08e5ea7a636e6cd307663ae13d1dcf50fa26856) docs: add vuinputd ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -0) </details> ### 📄 Description <!--- NOTE: DO NOT DELETE ANY COMMENTS OR SECTIONS OF THIS TEMPLATE. THEY ARE IMPORTANT FOR THE MAINTAINERS. IT IS OKAY TO LEAVE SECTIONS EMPTY AND BOXES UNCHECKED IF THEY DO NOT APPLY TO YOUR PR. ---> ## Description Add entry of vuinputd as mentioned on https://github.com/LizardByte/Sunshine/issues/3768 vuinputd is a Linux daemon for creating and forwarding virtual input devices, designed for sandboxed or containerized Sunshine setups. Use "Enabling container-friendly input handling for Sunshine on Linux." as short description. ### Screenshot <!--- Include screenshots if the changes are UI-related. ---> ### Issues Fixed or Closed <!--- If this PR fixes or closes any issues, please list them here. ---> <!--- Close issue example: `- Closes #1` ---> <!--- Fix bug issue example: `- Fixes #2` ---> <!--- Resolve issue example: `- Resolves #3` ---> #### Roadmap Issues <!--- If this PR solves any roadmap issues (https://github.com/LizardByte/roadmap/issues), please list them here. ---> <!--- e.g. `- Closes https://github.com/LizardByte/roadmap/issues/1` ---> ## Type of Change <!--- Select the type of change your PR introduces. You can select multiple types. ---> - [ ] **feat**: New feature (non-breaking change which adds functionality) - [ ] **fix**: Bug fix (non-breaking change which fixes an issue) - [x] **docs**: Documentation only changes - [ ] **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing semicolons, etc.) - [ ] **refactor**: Code change that neither fixes a bug nor adds a feature - [ ] **perf**: Code change that improves performance - [ ] **test**: Adding missing tests or correcting existing tests - [ ] **build**: Changes that affect the build system or external dependencies - [ ] **ci**: Changes to CI configuration files and scripts - [ ] **chore**: Other changes that don't modify src or test files - [ ] **revert**: Reverts a previous commit - [ ] **BREAKING CHANGE**: Introduces a breaking change (can be combined with any type above) ## Checklist <!--- Please check all applicable boxes. If a box does not apply, leave it unchecked. ---> - [x] Code follows the style guidelines of this project - [x] Code has been self-reviewed - [ ] Code has been commented, particularly in hard-to-understand areas - [ ] Code docstring/documentation-blocks for new or existing methods/components have been added or updated - [ ] Unit tests have been added or updated for any new or modified functionality ### AI Usage <!--- Select the option that best describes AI usage in this PR (choose only one). ---> - [ ] **None**: No AI tools were used in creating this PR - [x] **Light**: AI provided minor assistance (formatting, simple suggestions) - [ ] **Moderate**: AI helped with code generation or debugging specific parts - [ ] **Heavy**: AI generated most or all of the code changes --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-05-12 13:08:47 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
dependencies
pull-request
Mirrored from GitHub Pull Request
 ⭐ top issues dashboard
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-sunshine#455
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?