Most of what I have built belongs to somebody else. These are the ones that do not — small tools written to scratch my own itch, kept public in case the itch was not only mine.
They are all works in progress, and none of them are asking to be depended on. Have a look around anyway; issues and pull requests are welcome.
Repositories #
org-roam-to-obsidian
usage: convert.py [-h] [-i INPUT] [-o OUTPUT] [-p PROPERTIES [PROPERTIES ...]]
[--no-created] [--title-heading] [--keep-dead-links]
[--publish-when PROPERTY=VALUE] [--publish-key KEY]
[--created-key KEY [KEY ...]] [--modified-key KEY [KEY ...]]
[--no-modified] [--created-property CREATED_PROPERTY]
Convert org-roam files to Obsidian markdown format
options:
-h, --help show this help message and exit
-i, --input INPUT Input directory containing org-roam files (default:
~/Documents/slip-box)
-o, --output OUTPUT Output directory for markdown files (default:
./output)
-p, --properties PROPERTIES [PROPERTIES ...]
Org-mode properties to extract (e.g., filetags
roam_refs)
--no-created Disable adding created timestamp from filename
--title-heading Repeat the title as an H1 at the top of the body. Off
by default, because Obsidian and Quartz already show
it
--keep-dead-links Keep wikilinks whose target does not exist, instead of
unwrapping them
--publish-when PROPERTY=VALUE
Mark a note for publishing when it carries this org
property value, for example category=public
--publish-key KEY Frontmatter key for the publish flag (default:
publish)
--created-key KEY [KEY ...]
One or more frontmatter keys for the created timestamp
(default: created). Quartz also reads created_at and
date
--modified-key KEY [KEY ...]
One or more frontmatter keys for the modified
timestamp (default: modified). Quartz also reads
lastmod, updated and last-modified
--no-modified Disable adding the modified timestamp from the org
file's mtime
--created-property CREATED_PROPERTY
Use a specific org-mode property for created timestamp
instead of filename
gwttr
Weather report: honolulu
\ / Clear
.-. 26 °C
― ( ) ― ↙ 23 km/h
`-’ 10 km
/ \ 0.0 mmWashy Washy
washy-washy-cli
Fijn/Zijde, so does the card.
Usage: bun run generate [csv] [--out <dir>] [--machine <file>]
csv instruction CSV to read (default: data/washing-instructions.csv,
falling back to the committed .dist)
--out <dir> where the six PDFs go (default: out)
--machine <file> the appliances to draw (default: data/machine.json,
falling back to the committed .dist)
washy-washy-web
Live demo
washy-washy-core
@washy-washy/core — checks a CSV or JSON laundry chart against your washing machine and iron, and works out which piles can share a drum. One entry point for Node or Bun with CSV parsing, and a browser build that reads and writes charts as JSON instead.
washy-washy-pdf
@washy-washy/pdf.
form-handler
Accepts contact form submissions over HTTP and emails them on.
Configured from the environment, or from a forms file when FORMS_FILE
is set. See the README for the variables it reads.
Usage:
form-handler [flags]
Flags:
--healthcheck probe the local /healthz and exit
-h, --help help for form-handler
-v, --version version for form-handler
backup-git-repos
.tar.gz alongside the mirror.Back up git repositories from GitLab, Forgejo, and GitHub
Usage:
backup-git-repos [command]
Available Commands:
completion Generate the autocompletion script for the specified shell
config Manage the backup-git-repos config file
help Help about any command
list Print what would be backed up, clone nothing
run Mirror repositories from the configured forges
version Print the version
Flags:
-c, --config string config file (default: $XDG_CONFIG_HOME/backup-git-repos/config.yaml)
-h, --help help for backup-git-repos
Use "backup-git-repos [command] --help" for more information about a command.
tempus-fugit
Live demo