diff --git a/README.md b/README.md index 54a3cc3..35d6fb5 100644 --- a/README.md +++ b/README.md @@ -7,9 +7,10 @@ a CLI tool to post updates to crunk-scheduler. * [and this one](https://betterprogramming.pub/building-cli-apps-in-rust-what-you-should-consider-99cdcc67710c) ## Make working software first -* `crunk-update -p "text"` should make a paragraph of `
text
` in [crunk-scheduler](https://git.vvvvvvaria.org/crunk/crunk-scheduler) -* this is now possible and working. up next we should make some CLI flags such as --help -* and look up how to schedule a post +* `crunk-update --text "text"` should make a paragraph of `text
` in [crunk-scheduler](https://git.vvvvvvaria.org/crunk/crunk-scheduler) +* `crunk-update --file "test.md"` should post a markdown file to [crunk-scheduler](https://git.vvvvvvaria.org/crunk/crunk-scheduler) and have it converted to html +* this is now possible and working. up next we should make some CLI flags such as --help (done through using clap) + ## Learning Rust. * [clap is a Command Line Argument Parser for Rust](https://docs.rs/clap/latest/clap/) @@ -17,9 +18,12 @@ a CLI tool to post updates to crunk-scheduler. * [Tokio is an asynchronous runtime for the Rust programming language.](https://tokio.rs/) ## Readme driven development -* have crunk-scheduler do all the conversion to html in rss. +* have crunk-scheduler do all the conversion to html in rss. ✅ * make this as simple as possible - - post a simple text - - post markdown + - post a simple text ✅ + - post markdown ✅ - post media files (jpeg, mp3, mp4 etc) * be able to set a time when something is scheduled. +* and look up how to schedule a post +* have the url in a config file +* have the api-key in a config file (yes, everyone loves tokens, but this project is small)