a CLI tool to post updates to crunk-scheduler.
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.
|
|
|
|
# crunk-update
|
|
|
|
|
|
|
|
|
|
a CLI tool to post updates to crunk-scheduler.
|
|
|
|
|
|
|
|
|
|
## Designing CLI tools
|
|
|
|
|
I actually never did this properly. currently reading [this guide](https://clig.dev/)
|
|
|
|
|
|
|
|
|
|
## 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)
|
|
|
|
|
|
|
|
|
|
## Existential crisis
|
|
|
|
|
* ideally a tool on your machine should be easy to install
|
|
|
|
|
* python versions, venvs etc feels more like a problem here than in a web application
|
|
|
|
|
* attempt to write something in rust?
|
|
|
|
|
* currently following some rust tutorials
|
|
|
|
|
|
|
|
|
|
## Readme driven development
|
|
|
|
|
* have crunk-scheduler do all the conversion to html in rss.
|
|
|
|
|
* make this as simple as possible
|
|
|
|
|
- post a simple text
|
|
|
|
|
- post markdown or html snippets
|
|
|
|
|
- post files
|
|
|
|
|
* be able to set a time when something is scheduled.
|
