Project

picoflux

active

Miniflux fork using embedded pure-Go SQLite, WAL and FTS5 instead of PostgreSQL.

Overview

picoflux is an unofficial Miniflux fork that replaces PostgreSQL with an embedded pure-Go SQLite database. The result is one static binary and one database file, without CGo or a separate database service.

The feed reader, web interface and compatible APIs remain recognisably Miniflux. The fork-specific work is the storage, search, migration and release model.

How it works

Feed refresh and article extraction feed the normal Miniflux application services. Entries, users and configuration live in one SQLite database opened with WAL, a busy timeout and foreign-key enforcement.

Triggers maintain an FTS5 index. Search uses weighted BM25 ranking with a recency contribution, while PRAGMA user_version tracks the consolidated SQLite schema.

Features
Embedded database

Uses modernc.org/sqlite; no PostgreSQL server, libpq or CGo is required.

Full-text search

FTS5 triggers keep search data current, with title-weighted BM25 ranking and a recency boost.

Static deployment

Pure-Go builds support straightforward cross-compilation, static release binaries and multi-architecture containers.

Consolidated schema

Replaces the long PostgreSQL migration history with a single SQLite baseline and explicit schema version.

Miniflux compatibility

Retains the web interface, REST API, Fever API, Google Reader API and normal feed-processing behaviour.

Fresh import boundary

There is no automatic PostgreSQL migration. Existing installations export OPML and import it into a new Picoflux database.

Architecture
RSS / Atom feeds scheduled refresh Miniflux services fetch · parse · scrape SQLite database WAL · foreign keys FTS5 search triggers · BM25 · recency Picoflux server web · REST · Fever · GReader Readers browser · mobile clients Miniflux feed processing with embedded SQLite storage