crunk/crunk-scheduler
1
0
Fork 0
Code Issues 1 Pull Requests Projects Releases Wiki Activity
webapi where you can request scheduled rss feed publishing
8 Commits 1 Branch 0 Tags 64 KiB
Python 94.1%
Mako 5.9%
396e41dd8c
Go to file
crunk 396e41dd8c put posts in database
2023-10-01 21:35:14 +02:00
instance start of a sqlitedb 2023-07-19 22:30:33 +02:00
migrations start of a sqlitedb 2023-07-19 22:30:33 +02:00
models put posts in database 2023-10-01 21:35:14 +02:00
scheduler put posts in database 2023-10-01 21:35:14 +02:00
__init.py__ put posts in database 2023-10-01 21:35:14 +02:00
.gitignore the smallest swiss knive 2023-07-19 19:46:49 +02:00
app.py start of a sqlitedb 2023-07-19 22:30:33 +02:00
deploydb.py start of a sqlitedb 2023-07-19 22:30:33 +02:00
LICENSE Initial commit 2023-07-18 19:31:58 +02:00
pyproject.toml the smallest swiss knive 2023-07-19 19:46:49 +02:00
README.md README driven development 2023-07-20 09:35:44 +02:00
requirements.txt something that works 2023-07-19 21:36:31 +02:00
start.py put posts in database 2023-10-01 21:35:14 +02:00

README.md

crunk-scheduler

webapi where you can request scheduled rss feed publishing. part of the crunk suite of software

readme driven development

  • crunk-scheduler should be able to take post request from other applications

    • set the time something should be added to the rss feed.
    • what should be added to the rss feed (think logbot style options)
    • optional: multiple feeds, specify which feed.
    • handle with Flask (could look into flask api packages)

  • crunk-scheduler should have a simple database (sqlite maybe) where the scheduled posts are stored.

    • store files on disk not in db.
    • use Flask-SQLAlchemy and Flask-Migrate

  • periodically check if there are new things that need to be posted.

    • check db and use Flask-APScheduler

  • generate the rss feed.

    • use feedgenerator
    • serve rss from static folder using Flask Blueprint