Skip to main content

History4Feed

Project description

history4feed

codecov

Overview

It is common for feeds (RSS or XML) to only include a limited number of posts. I generally see the latest 3 - 5 posts of a blog in a feed. For blogs that have been operating for years, this means potentially thousands of posts are missed.

There is no way to page through historic articles using an RSS or ATOM feed (they were not designed for this), which means the first poll of the feed will only contain the limited number of articles in the feed. This limit is defined by the blog owner.

history4feed can be used to create a complete history for a blog and output it as an RSS feed.

history4feed offers an API interface that;

  1. takes an RSS / ATOM feed URL
  2. downloads a Wayback Machine archive for the feed
  3. identified all unique blog posts in the historic feeds downloaded
  4. downloads a HTML version of the article content on each page
  5. stores the post record in the databases
  6. exposes the posts as JSON or XML RSS

tl;dr

history4feed

Watch the demo.

Install

Download and configure

# clone the latest code
git clone https://github.com/muchdogesec/history4feed

Configuration options

history4feed has various settings that are defined in an .env file.

To create a template for the file:

cp .env.example .env

To see more information about how to set the variables, and what they do, read the .env.markdown file.

Build the Docker Image

sudo docker compose build

Start the server

sudo docker compose up

Access the server

The webserver (Django) should now be running on: http://127.0.0.1:8002/

You can access the Swagger UI for the API in a browser at: http://127.0.0.1:8002/api/schema/swagger-ui/

Useful supporting tools

Support

Minimal support provided via the DOGESEC community.

License

Apache 2.0.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

history4feed-0.0.2.tar.gz (157.2 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

history4feed-0.0.2-py3-none-any.whl (45.1 kB view details)

Uploaded Python 3

File details

Details for the file history4feed-0.0.2.tar.gz.

File metadata

  • Download URL: history4feed-0.0.2.tar.gz
  • Upload date:
  • Size: 157.2 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.12.9

File hashes

Hashes for history4feed-0.0.2.tar.gz
Algorithm Hash digest
SHA256 a6e921582a7739f628afc3926e7bd1b6438415732b41903a752e8df06dcd01e9
MD5 47e78d35fc41da2e419ebe4b06f6c55d
BLAKE2b-256 2f84524fd2007a8822880e9a538b8c0f3ddc38fa19dc61f75400a191aa9a724e

See more details on using hashes here.

Provenance

The following attestation bundles were made for history4feed-0.0.2.tar.gz:

Publisher: create-release.yml on muchdogesec/history4feed

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file history4feed-0.0.2-py3-none-any.whl.

File metadata

  • Download URL: history4feed-0.0.2-py3-none-any.whl
  • Upload date:
  • Size: 45.1 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.12.9

File hashes

Hashes for history4feed-0.0.2-py3-none-any.whl
Algorithm Hash digest
SHA256 5c0f4cb9c70e6c07d9569262b993007461758c14df2b07674b103e837eb449f3
MD5 eeb8bcf97edb803fa88f545a69e96c1a
BLAKE2b-256 174befb0edeb1e01502b86dd6456ed319b05656c7f7359857721064f209356bf

See more details on using hashes here.

Provenance

The following attestation bundles were made for history4feed-0.0.2-py3-none-any.whl:

Publisher: create-release.yml on muchdogesec/history4feed

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page