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
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
7 Commits
1 Branch
0 Tags
64 KiB
 
 
Tree: 53a9f313c0
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '53a9f313c0'
${ noResults }
crunk 53a9f313c0
README driven development 		1 year ago
instance start of a sqlitedb 1 year ago
migrations start of a sqlitedb 1 year ago
.gitignore the smallest swiss knive 1 year ago
LICENSE Initial commit 1 year ago
README.md README driven development 1 year ago
app.py start of a sqlitedb 1 year ago
deploydb.py start of a sqlitedb 1 year ago
postmodel.py start of a sqlitedb 1 year ago
pyproject.toml the smallest swiss knive 1 year ago
requirements.txt something that works 1 year ago
start.py start of a sqlitedb 1 year ago

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