|
|
@ -3,16 +3,15 @@ |
|
|
a CLI tool to post updates to crunk-scheduler. |
|
|
a CLI tool to post updates to crunk-scheduler. |
|
|
|
|
|
|
|
|
## Designing CLI tools |
|
|
## Designing CLI tools |
|
|
I actually never did this properly. currently reading [this guide](https://clig.dev/) |
|
|
* I actually never did this properly. currently reading [this guide](https://clig.dev/) |
|
|
|
|
|
* [and this one](https://betterprogramming.pub/building-cli-apps-in-rust-what-you-should-consider-99cdcc67710c) |
|
|
|
|
|
|
|
|
## Make working software first |
|
|
## Make working software first |
|
|
* `crunk-update -p "text"` should make a paragraph of `<p>text</p>` in [crunk-scheduler](https://git.vvvvvvaria.org/crunk/crunk-scheduler) |
|
|
* `crunk-update -p "text"` should make a paragraph of `<p>text</p>` in [crunk-scheduler](https://git.vvvvvvaria.org/crunk/crunk-scheduler) |
|
|
|
|
|
|
|
|
## Existential crisis |
|
|
## Learning Rust. |
|
|
* ideally a tool on your machine should be easy to install |
|
|
* [clap is a Command Line Argument Parser for Rust](https://docs.rs/clap/latest/clap/) |
|
|
* python versions, venvs etc feels more like a problem here than in a web application |
|
|
* [reqwest is a convenient, higher-level HTTP Client](https://docs.rs/reqwest/latest/reqwest/) |
|
|
* attempt to write something in rust? |
|
|
|
|
|
* currently following some rust tutorials |
|
|
|
|
|
|
|
|
|
|
|
## Readme driven development |
|
|
## 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. |
|
|
|
