Getting Started¶
Welcome to Bootible! Setting up a gaming handheld follows the same four steps every time — and the docs are organized in that order.
Your journey¶
-
Get started
Preview Bootible with zero setup, then put your own settings in a config repo you can edit from any browser.
-
Configure your device
Pick what your device should have — apps, streaming, emulation, power fixes — using your platform's options.
-
Install & run
Run the one-liner, review the preview, type
bootibleto apply. -
Post install
Read your receipt, know what stays manual, and re-run after Windows updates to repair drift.
In this section: Try It in 5 Minutes (the zero-config preview), Your Config Repo (make it yours), Config Basics (how config works), and Multi-Device (one repo, many handhelds).
Frequently Asked Questions¶
Is it safe to run?
Yes! Bootible runs in dry-run mode by default. The first run shows you exactly what would happen without making any changes. Only when you run bootible afterward are changes applied.
Additionally:
- Windows: Creates a System Restore Point before making changes
- Steam Deck: Creates a btrfs snapshot before making changes
Do I need a GitHub account?
No, GitHub is optional. Without it:
- You can still run Bootible with default settings
- Logs are saved locally instead of pushed to a repo
- You miss out on syncing configs across devices
With a GitHub account:
- Store your personal configuration in a private repo
- Sync settings across multiple devices
- Run logs are automatically pushed for debugging
Can I undo changes?
Yes!
- Windows: Use System Restore to revert to the pre-Bootible state
- Steam Deck: Restore from the btrfs snapshot created before running
What if I run it multiple times?
Bootible is idempotent — running it multiple times is safe. It will:
- Skip packages already installed
- Update configurations if they've changed
- Not duplicate any settings