mirror of
https://github.com/lrnselfreliance/wrolpi.git
synced 2026-10-26 19:01:39 -04:00
Create your own off-grid library
https://wrolpi.org
49dcb25d8e
* Persist finalize_download mutations; isolate child-download enqueue A channel/RSS Download could get stuck permanently "pending". Root cause: the phase-split dispatch in signal_download_download passes the Download loaded in an already-closed session to finalize_download, so it is DETACHED. ChannelDownloader.finalize_download sets `download.sub_downloader = 'video'` (and info_json/collection_id) on that detached object, so the write never reaches the DB. The status block then re-queries the Download fresh, reads sub_downloader=None, and calls create_downloads(downloader_name=None) -> `InvalidDownload: Cannot find downloader with name None`. That exception was raised inside the status-commit transaction (outside the inner try), so it (a) rolled back the parent's complete(), reverting it to the `pending` set by started(), and (b) was swallowed by the outer bare `except Exception`, which only logs. Result: the parent never failed, never completed — it sat `pending` forever, re-crashing the same way on every restart. Fixes: - finalize_download is now given a Download re-loaded in (attached to) its own session, so its mutations persist. - Child-download creation moves to its own transaction after the parent's status is committed. A failure there is logged and cannot roll back or strand the parent. The existing test harness reuses one shared DB session for every get_db_session call, so detached-object and rollback bugs never reproduced under it (which is why this shipped). Add `production_like_sessions` to conftest.py — a context manager handing out a fresh Session per call, like production — and two regression tests that fail without the fix. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * Re-attach Download in prepare_download too (consistency) prepare_download receives the same detached Download as finalize_download did, so VideoDownloader.prepare_download's writes to the row (destination/tag_names) are not reliably persisted. Re-load the Download attached to the prepare session, mirroring the finalize fix, so the row's metadata is accurate. Unlike sub_downloader (which the status block re-reads and feeds to create_downloads), nothing downstream re-reads these values, so this is a consistency/cosmetic improvement, not a functional bug — and it cannot be made to fail in a test (the loaded Download's session outlives the worker), so no dedicated test is added. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * Log (not swallow) session-close failures in production_like_sessions Addresses Greptile review: surface a failed session.close() at debug level instead of silently passing. engine.dispose() still does the authoritative cleanup, so the close failure remains non-fatal. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .circleci | ||
| .github | ||
| .run | ||
| alembic | ||
| app | ||
| controller | ||
| debian-live-config | ||
| docker | ||
| etc | ||
| modules | ||
| pi-gen | ||
| release | ||
| scripts | ||
| test | ||
| wrolpi | ||
| .coveragerc | ||
| .dockerignore | ||
| .gitignore | ||
| .gitmodules | ||
| .gitpod.yml | ||
| .mcp.json.example | ||
| alembic.ini | ||
| conftest.py | ||
| demo_link.jpg | ||
| docker-compose.yml | ||
| help.sh | ||
| icon.ico | ||
| icon.png | ||
| INSTALL.md | ||
| install.sh | ||
| join_discord.png | ||
| LICENSE | ||
| main.py | ||
| pytest.ini | ||
| README.md | ||
| repair.sh | ||
| requirements.txt | ||
| test_all.sh | ||
| UPGRADE.md | ||
| upgrade.sh | ||
WROLPi
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.
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 | yes | yes | Protomaps |
| Podcasts/Audio | yes | planned | planned |
Demo
Download
Images are available at wrolpi.org
Try WROLPi!
You can try out WROLPi by running the docker containers.
- Install docker-ce and docker-compose
- Copy the latest WROLPi code.
git clone https://github.com/lrnselfreliance/wrolpi.git
- Change directory into the code base.
cd wrolpi
- Initialize git submodules
git submodule update --init
- Build the containers.
docker-compose build --parallel
- Create volumes.
docker volume create --name=openstreetmap-datadocker volume create --name=openstreetmap-rendered-tiles
- Start the database.
docker-compose up -d db
- Initialize the database.
docker-compose run --rm api db upgrade
- Start the docker containers.
docker-compose up
- Browse to WROLPi.
More Docker documentation is available in docker/README.md
Install WROLPi
Full installation instructions are in INSTALL.md. Pick the option that matches your hardware:
- WROLPi Portable (Live USB) — boot a complete WROLPi from a USB stick on any x86 PC or laptop. Nothing is installed to the computer; the first boot creates a persistence partition on the USB so your library, database, and configuration survive reboots.
- Debian 12 — install WROLPi onto an x86 PC or laptop.
- Raspberry Pi — install WROLPi onto a Raspberry Pi with an external drive.
- Docker — run the WROLPi containers on an existing Linux host.
Charter
Guiding Principals
- Storage is cheaper than power.
- Two is one, one is none.
- Run silently.
- Primary, secondary, tertiary.
- Secure as a bookshelf in your home.
Physical properties
- 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.
- 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
- 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
- A WROLPi instance should be able to "factory-reset" itself without any outside services.
- WROLPi should function completely without any internet services.
- 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.
- 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.
- 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!
