Create your own off-grid library.

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.

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

• Features
• Demo
• Download
• Try WROLPi
• Debian 12 Install
• Raspberry Pi Install
• Charter
• Upgrading WROLPi
• Join

• 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

Images are available at wrolpi.org

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. Build the containers.
   • docker-compose build --parallel
5. Create volumes.
   • docker volume create --name=openstreetmap-data
   • docker volume create --name=openstreetmap-rendered-tiles
6. Start the database.
   • docker-compose up -d db
7. Initialize the database.
   • docker-compose run --rm api db upgrade
8. Start the docker containers.
   • docker-compose up
9. Browse to WROLPi.
   • http://0.0.0.0:8080

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 http://wrolpi.local or the IP address of your WROLPi!

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 http://wrolpi.local or the IP address of your WROLPi!

1. Storage is cheaper than power.
2. Two is one, one is none.
3. Run silently.

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.

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.

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 our Discord