Create your own off-grid library https://wrolpi.org
Find a file
2026-03-05 15:02:23 -07:00
.circleci Running FE jest tests on github. 2025-12-06 15:11:37 -07:00
.github/workflows Creating Controller service which will control WROLPi services, admin, SMART, disks, and status. nginx will fallback to Controller UI when React UI is unavailable (such as during upgrades). 2025-12-15 15:48:40 -07:00
.run Video downloads have many more options. Downloads are migrated. 2024-11-28 09:48:57 -07:00
alembic Changing video view_count to bigint for popular videos. 2026-02-08 12:33:37 -07:00
app Bump minimatch in /app 2026-02-28 08:43:14 -07:00
controller Enabling fallback on first controller repair run so that main ui launches after repair completion. 2026-03-01 12:42:20 -07:00
debian-live-config Removing redundant web app build during image builds. 2026-02-27 17:22:46 -07:00
docker Bumping wrolpi-help to include new docs. 2026-02-23 17:30:24 -07:00
etc Allowing CORS from Controller :8087 to API to know when first repair has completed. 2026-02-27 19:56:18 -07:00
modules Storing parent_download_url in a file group's json file after download has completed. 2026-03-03 15:54:22 -07:00
pi-gen Removing redundant web app build during image builds. 2026-02-27 17:22:46 -07:00
scripts Creating script to clean up orphaned tag files. 2026-02-28 17:05:02 -07:00
test Bumping python requirements versions. 2024-10-16 18:56:41 -06:00
wrolpi Bumping yt-dlp. 2026-03-05 15:02:23 -07:00
.coveragerc Adding coverage config which ignores non-API directories. 2024-10-16 18:56:03 -06:00
.dockerignore A new start 2021-11-01 16:43:09 -06:00
.gitignore Removing WROLPi admin functionality that is now in Controller. 2025-12-19 18:41:27 -07:00
.gitmodules Adding FileGroup.published_date/author/etc. Creating script which converts a Singlefile to an Archive FileGroup files. 2023-10-23 18:09:08 -06:00
.gitpod.yml add Gitpod support (#157) 2023-02-02 16:02:19 -07:00
.mcp.json.example Removing WROLPi admin functionality that is now in Controller. 2025-12-19 18:41:27 -07:00
alembic.ini A new start 2021-11-01 16:43:09 -06:00
conftest.py Zim/Kiwix (Wikipedia) feature 2023-07-10 21:30:40 -06:00
demo_link.jpg Replacing demo image. 2023-01-30 13:27:26 -07:00
docker-compose.yml Updating download process to prevent rate limiting. 2026-02-21 14:08:00 -07:00
help.sh Creating Controller service which will control WROLPi services, admin, SMART, disks, and status. nginx will fallback to Controller UI when React UI is unavailable (such as during upgrades). 2025-12-15 15:48:40 -07:00
icon.ico A new start 2021-11-01 16:43:09 -06:00
icon.png Zim/Kiwix (Wikipedia) feature 2023-07-10 21:30:40 -06:00
install.sh Many fixes split out from the feature/unified-query branch. Installing diagnostic tools in the built images. Displaying video comment statistics. Echoing error when install.sh fails. 2024-04-14 13:13:30 -06:00
join_discord.png A new start 2021-11-01 16:43:09 -06:00
LICENSE A new start 2021-11-01 16:43:09 -06:00
main.py Using shared context to sync cookies between processes. 2026-02-22 14:32:27 -07:00
pytest.ini FileGroups in Collections can be reorganized in the Collection's directory. 2026-01-31 18:08:41 -07:00
README.md Adding new Guiding Principal. 2025-01-01 17:58:03 -07:00
repair.sh Clearing cached python files in repair.sh. Creating reset_virtual_environments.sh script which deletes the virtual environments and rebuilds them (requires internet) 2026-02-28 16:11:12 -07:00
requirements.txt Bumping yt-dlp. 2026-03-05 15:02:23 -07:00
test_all.sh Creating test_all.sh script to run all frontend and backend tests. 2025-12-17 15:11:57 -07:00
UPGRADE.md Combining install scripts into a new repair script. Removing create_db script in favor of repair script. 2023-10-03 12:15:29 -06:00
upgrade.sh Changing ownership of tmp upgrade file so that wrolpi-upgrade can change it. 2026-02-05 08:52:54 -07:00

WROLPi

Build Status License: GPL v3 Discord Gitpod

Create your own off-grid library.

WROLPi Logo

WROLPi is a self-contained collection of software to help you survive the world Without Rule of Law.

WROLPi is intended to be run on a Raspberry Pi with an optional external drive attached. It serves up it's own Wi-Fi network so that any user with a laptop/tablet/phone can connect and use the library created by the maintainer.

WARNING WROLPi is under active development!

  • WROLPi is in Beta!
  • Expect things to change!

Table of Contents

Features

  • Videos
  • Web Archives
  • Maps
  • Wikipedia
  • File search
  • eBooks (EPUB / PDFs)
  • Wi-Fi Hotspot
  • Universal search
  • Food Inventory management
  • One-Time pad generator, encrypter/decrypter
  • Synchronizer/duplicator
  • Food storage calculator

Module features matrix

Module View Search Download Project
Videos yes yes yes yt-dlp
Web Archives yes yes yes Singlefile
Wikipedia yes yes yes Kiwix
eBooks yes yes planned EPUB/PDF
Map yes planned planned OpenStreetMap
Podcasts/Audio yes planned planned

Demo

YouTube Demo Video

Download

Images are available at wrolpi.org

Try WROLPi!

You can try out WROLPi by running the docker containers.

  1. Install docker-ce and docker-compose
  2. Copy the latest WROLPi code.
    • git clone https://github.com/lrnselfreliance/wrolpi.git
  3. Change directory into the code base.
    • cd wrolpi
  4. Initialize git submodules
    • git submodule update --init
  5. Build the containers.
    • docker-compose build --parallel
  6. Create volumes.
    • docker volume create --name=openstreetmap-data
    • docker volume create --name=openstreetmap-rendered-tiles
  7. Start the database.
    • docker-compose up -d db
  8. Initialize the database.
    • docker-compose run --rm api db upgrade
  9. Start the docker containers.
    • docker-compose up
  10. Browse to WROLPi.

Debian 12 Install

Steps necessary to initialize your WROLPi after installing the Debian image from wrolpi.org

  1. Download and copy a pre-built Debian image from https://wrolpi.org onto a USB thumb-drive (USB 2 recommended)
  2. Insert the thumb-drive into the laptop, boot to the thumb-drive
    1. Select "Start Installer"
    2. Install Debian 12 as you would like.
      1. It is recommended to use the hostname wrolpi
      2. (WROLPi will be installed during the installation without your intervention.)
  3. Unplug the thumb-drive after the installation has completed
  4. Login as the user you created during installation.
  5. Switch to the root user: su -
  6. Initialize the WROLPi databases using the repair script: /opt/wrolpi/repair.sh
  7. Reboot: reboot
  8. Browse to https://wrolpi.local or the IP address of your WROLPi!

Raspberry Pi Install

Steps necessary to initialize your WROLPi after installing the Raspberry Pi image from wrolpi.org

  1. Download and copy a pre-built image from https://wrolpi.org onto an SD card.
  2. Boot the Raspberry Pi, login with username pi and password wrolpi.
  3. Modify fstab to mount your external drive to /media/wrolpi (modify this command to match your system).
    • echo '/dev/sda1 /media/wrolpi auto defaults,nofail 0 0' | sudo tee -a /etc/fstab
  4. Initialize the WROLPi databases using the repair script: sudo /opt/wrolpi/repair.sh
  5. Reboot sudo reboot
  6. Join the Hotspot or browse to https://wrolpi.local or the IP address of your WROLPi!

Charter

Guiding Principals

  1. Storage is cheaper than power.
  2. Two is one, one is none.
  3. Run silently.
  4. Primary, secondary, tertiary.
  5. Secure as a bookshelf in your home.

Physical properties

  1. A WROLPi instance should be capable of running with a minimal of hardware:
    • Raspberry Pi
    • SD card
    • External USB hard drive
    • Power supply and cables
    • Wi-Fi USER device such as a phone, tablet, or laptop.
  2. A WROLPi instance should consume a minimal amount of electricity during WROL event. It is expected power will be scarce when WROLPi is needed most.

User expectations

  1. A WROLPi instance should be run and maintained by a person (MAINTAINER) with a moderate amount of Linux and Raspberry Pi experience. It is expected that they should be able to do this using only the documentation on their WROLPi.

Software properties and capabilities

  1. A WROLPi instance should be able to "factory-reset" itself without any outside services.
  2. WROLPi should function completely without any internet services.
  3. A user should have easy access to their data if WROLPi fails:
    • For example, a user can watch their videos by navigating a short and intuitive directory structure and opening the video in their preferred video player.
  4. WROLPi should be self-documented. The UI should contain a tutorial for USERS as well as the MAINTAINER.
    • If the UI isn't functional, the code should be documented such that a user can restore functionality.
  5. WROLPi should favor pre-processing, rather than processing during a WROL event. Such as re-encoding a video, or processing captions. This is to ensure that when a user adds content during non-WROL time, the processing for optimum performance is already done for a WROL event.

Join!

Discord QR Code

Join our Discord