Resolves https://github.com/tiny-pilot/tinypilot/issues/1689 By default, Playwright limits each test to a 30s runtime. Unfortunately, when the the test reaches its timeout, it displays an opaque error message: <img width="331" alt="Screen Shot 2023-12-05 at 14 42 47" src="https://github.com/tiny-pilot/tinypilot/assets/6730025/e44424f0-89f3-4569-98b2-7dd3a8dde7ee"> In this case, the test timed out because one of the license URLs took >30s to respond. To avoid this issue, I've applied a 10s timeout to each license URL check. ### Notes 1. I couldn't find a way to catch the actual test's [TimeoutError](https://playwright.dev/docs/api/class-timeouterror) or how to set a custom test timeout message 🤷♂️ 2. I tested this PR via * https://github.com/tiny-pilot/tinypilot/pull/1701 * https://github.com/tiny-pilot/tinypilot/pull/1702 <a data-ca-tag href="https://codeapprove.com/pr/tiny-pilot/tinypilot/1700"><img src="https://codeapprove.com/external/github-tag-allbg.png" alt="Review on CodeApprove" /></a>
|2 days ago|
|.circleci||4 weeks ago|
|.dependabot||3 years ago|
|.github||6 months ago|
|.vscode||3 months ago|
|app||1 week ago|
|bundler||1 month ago|
|debian-pkg||1 month ago|
|dev-scripts||2 months ago|
|docs||5 months ago|
|e2e||2 days ago|
|hooks||7 months ago|
|readme-assets||9 months ago|
|scripts||1 month ago|
|.dockerignore||6 months ago|
|.eslintrc.cjs||7 months ago|
|.gitignore||6 months ago|
|.lintianignore||6 months ago|
|.prettierignore||6 months ago|
|.pylintrc||3 months ago|
|.ruff.toml||3 months ago|
|.shellcheckrc||3 years ago|
|.style.yapf||3 years ago|
|.yapfignore||3 years ago|
|ARCHITECTURE.md||5 months ago|
|CONTRIBUTING.md||4 weeks ago|
|COPYRIGHT||7 months ago|
|LICENSE||2 years ago|
|MANIFEST.in||3 years ago|
|README.md||3 months ago|
|__init__.py||4 years ago|
|dev_app_settings.cfg||1 year ago|
|dev_requirements.txt||4 weeks ago|
|get-tinypilot.sh||6 months ago|
|package-lock.json||5 months ago|
|package.json||5 months ago|
|playwright.config.js||1 week ago|
|quick-install||1 year ago|
|requirements.txt||5 months ago|
|setup.py||3 years ago|
Turn your Raspberry Pi into a browser-based KVM.
- Video capture (HDMI/DVI/VGA)
- Keyboard forwarding
- Mouse forwarding
- Fullscreen mode
- Paste text from clipboard
TinyPilot official hardware packages give you everything you need to run TinyPilot and allows you to fund TinyPilot's development for future improvements.
Voyager 2a is TinyPilot's professional-grade KVM over IP device. Its quiet, compact design makes it a great fit for professional environments such as offices, data centers, and server rooms.
Build your own
- Raspberry Pi 4 (all variants work)
- HDMI to USB dongle
- They have no brand name, and there are several variants, but they're all built on the same MacroSilicon 2109 chip.
- They're available for $10-15 on eBay and AliExpress.
- 3 Amp power supply
- USB-C to USB-A cable (Male/Male)
- microSD card (Class 10, 8 GB or larger)
- HDMI to HDMI cable
- Or [other] to HDMI, depending on how your target machine displays output.
- (Optional) A USB-C OTG split connector: Supports continuous power when the target computer turns off.
- (Optional) VGA to HDMI Adapter - If your target system has VGA output.
- Alternatively, you can replace the VGA to HDMI adapter and HDMI to USB dongle with a VGA to USB adapter.
See "TinyPilot: Build a KVM Over IP for Under $100" for a more detailed tutorial on how to assemble these parts to create a TinyPilot.
- Raspberry Pi OS Bullseye (32-bit)
You can install TinyPilot on a compatible Raspberry Pi in just two commands.
curl \ --silent \ --show-error \ https://raw.githubusercontent.com/tiny-pilot/tinypilot/master/get-tinypilot.sh | \ bash - && \ sudo reboot
When your Pi reboots, you should be able to access TinyPilot by visiting your Pi hostname in the browser. For example, if your device is named
See the CONTRIBUTING file.
Other installation options
To update to the latest version of TinyPilot, run the update script:
/opt/tinypilot/scripts/upgrade && sudo reboot
If you're having trouble with TinyPilot, you can retrive logs from the web dashboard by clicking "Logs" in the bottom of the main dashboard.
If you can't access the web dashboard, you can retrieve the logs by SSHing into the device and running the following command:
This log is useful if you file a bug report.
You can read more details about the logs in the wiki.
TinyPilot does not support authentication or transport-level encryption. You should only use TinyPilot on networks that you trust. Anyone who accesses the TinyPilot URL can shutdown or restart your Pi and type arbitrary commands into the device to which your Pi is connected.
To use TinyPilot on untrusted networks, you can upgrade to TinyPilot Pro, which adds password-based authentication and TLS for end-to-end encryption.
As a free alternative, you can adjust your Nginx configuration (included by default with the installation) to require HTTP Basic Authentication and add a self-signed TLS certificate.
Detailed project updates
If you're interested in seeing what's happening with the project at a granular level, weekly updates appear every Friday on What Got Done:
- TinyPilot Wiki: Guides for tasks related to TinyPilot.
TinyPilot would not be possible without the excellent and generous work from many open source projects, the most notable of which are listed below:
For news about major TinyPilot releases and other updates about the project, sign up for the TinyPilot mailing list:
Upgrade to Pro
TinyPilot Pro includes additional features for professional users, including:
- Virtual drive mounting and booting
- Password-based authentication
Support the project and upgrade to Pro at https://tinypilotkvm.com/product/tinypilot-pro.