|
|
|
@ -5,15 +5,15 @@ webapi where you can request scheduled rss feed publishing. part of the crunk su |
|
|
|
## 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) |
|
|
|
- what should be added to the rss feed (now it can do text, md files, images soon?) |
|
|
|
- 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 |
|
|
|
- use Flask-SQLAlchemy and Flask-Migrate ✅ |
|
|
|
* periodically check if there are new things that need to be posted. |
|
|
|
- check db and use Flask-APScheduler |
|
|
|
- check db and use Flask-APScheduler ✅ |
|
|
|
* generate the rss feed. |
|
|
|
- use feedgenerator |
|
|
|
- serve rss from static folder using Flask Blueprint |
|
|
|
- use feedgenerator ✅ |
|
|
|
- serve rss from static folder using Flask Blueprint ✅ |
|
|
|
|
