How to set up Feedpushr with Docker Compose?

Use the YAML example in the README: define a service with the ncarlier/feedpushr image, map port 8080, and set volumes for persistent data storage. This automates deployment with restart policies.

Can Feedpushr post articles to Twitter?

Yes, but it requires an external plugin from the contrib directory, as Twitter support isn't built-in. You need to compile and load the plugin at startup, which adds complexity.

Feedpushr vs Miniflux: which is better for self-hosted RSS?

Feedpushr excels in automation and pushing content to outputs, ideal for distribution workflows. Miniflux is more focused on reading and managing feeds, so choose based on whether you need consumption or distribution.

How do I create a custom filter in Feedpushr?

Develop a Go plugin by writing code that compiles to a .so library, then load it using the --plugin flag or place it in the working directory. The README references external contributions for examples.

Does Feedpushr support real-time updates?

Yes, via WebSub protocol, allowing decentralized pubsub for immediate updates from supported feeds. This is mentioned in the features as a way to reduce polling delays.

What authentication methods does Feedpushr support?

It supports HTTP Basic Auth with htpasswd files and OpenID Connect (e.g., Google), configurable through environment variables like FP_AUTHN, as detailed in the authentication section.

Feedpushr — Self-Hosted Feed Aggregator

What is Feedpushr?

Feedpushr is a self-hosted feed aggregator daemon that collects articles from RSS/Atom feeds, processes them through a customizable filter chain, and pushes them to various outputs like HTTP endpoints, email, or external services. It solves the problem of automating content distribution and curation by providing a flexible, extensible pipeline that users control entirely on their own infrastructure.

Target Audience

Developers, sysadmins, or content curators who need to automate the aggregation and distribution of feed content, especially those preferring self-hosted solutions with custom processing rules.

Value Proposition

Developers choose Feedpushr for its simplicity as a single binary, its extensibility via plugins and expressions, and its full self-hosting capability, giving them complete control over their feed processing workflow without relying on third-party services.

A simple feed aggregator daemon with sugar on top.

Use Cases

Best For

Building a custom news aggregation and notification system
Automating content distribution to multiple channels (e.g., HTTP, email, social media)
Self-hosting a feed reader with advanced filtering and tagging
Creating ETL pipelines for feed data using shell tools or plugins
Implementing real-time feed updates via WebSub subscriptions
Developing internal tools for content curation with conditional routing

Not Ideal For

Users wanting a fully managed, cloud-based RSS reader with zero server maintenance
Projects needing out-of-the-box integrations with modern platforms like Slack or Discord without custom plugin development
Simple feed monitoring or one-time parsing without continuous aggregation and conditional routing

Pros & Cons

Pros

Single Binary Simplicity

Deploys as a standalone executable with an embedded database, eliminating complex dependencies, as shown in the installation options using Docker or direct download.

Extensible Plugin System

Supports custom filters and outputs via compiled Go plugins, allowing tailored workflows, with examples like Twitter integration available in the contrib directory.

Comprehensive Control Interfaces

Offers a REST API with OpenAPI documentation, a web UI, and a CLI, providing multiple ways to manage feeds and outputs, as detailed in the features section.

Powerful Conditional Logic

Uses a custom expression language to route articles based on tags, title, or metadata, enabling precise automation, documented in the EXPRESSION.md file.

Cons

Plugin Development Overhead

Creating custom outputs or filters requires Go programming and compiling plugins, which can be a barrier for non-developers, as admitted in the plugins section.

Limited Built-in Integrations

Core outputs are basic (e.g., stdout, HTTP, email), and advanced services like Twitter depend on external plugins that may lack maintenance or documentation.

Configuration Complexity

Setting up involves multiple environment variables, authentication files, and expression syntax, leading to a steeper initial setup compared to simpler aggregators.

What is Feedpushr?

Target Audience

Developers, sysadmins, or content curators who need to automate the aggregation and distribution of feed content, especially those preferring self-hosted solutions with custom processing rules.

Value Proposition

Use Cases

Best For

Building a custom news aggregation and notification system
Automating content distribution to multiple channels (e.g., HTTP, email, social media)
Self-hosting a feed reader with advanced filtering and tagging
Creating ETL pipelines for feed data using shell tools or plugins
Implementing real-time feed updates via WebSub subscriptions
Developing internal tools for content curation with conditional routing

Not Ideal For

Users wanting a fully managed, cloud-based RSS reader with zero server maintenance
Projects needing out-of-the-box integrations with modern platforms like Slack or Discord without custom plugin development
Simple feed monitoring or one-time parsing without continuous aggregation and conditional routing

Pros & Cons

Pros

Single Binary Simplicity

Deploys as a standalone executable with an embedded database, eliminating complex dependencies, as shown in the installation options using Docker or direct download.

Extensible Plugin System

Supports custom filters and outputs via compiled Go plugins, allowing tailored workflows, with examples like Twitter integration available in the contrib directory.

Comprehensive Control Interfaces

Offers a REST API with OpenAPI documentation, a web UI, and a CLI, providing multiple ways to manage feeds and outputs, as detailed in the features section.

Powerful Conditional Logic

Uses a custom expression language to route articles based on tags, title, or metadata, enabling precise automation, documented in the EXPRESSION.md file.

Cons

Plugin Development Overhead

Creating custom outputs or filters requires Go programming and compiling plugins, which can be a barrier for non-developers, as admitted in the plugins section.

Limited Built-in Integrations

Core outputs are basic (e.g., stdout, HTTP, email), and advanced services like Twitter depend on external plugins that may lack maintenance or documentation.

Configuration Complexity

Setting up involves multiple environment variables, authentication files, and expression syntax, leading to a steeper initial setup compared to simpler aggregators.

Feedpushr

What is Feedpushr?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?

Feedpushr

What is Feedpushr?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?