Skip to main content

Can I Hang My Washing Out

@aaronge/can-i-hang-my-washing-outv2026.11.05.2· 16d agoBEHAVIORSWORKFLOWS
01README

Scores whether it's worth hanging your washing out this morning and this afternoon, from free temperature/humidity/wind/rain/sunshine forecast data.

02Release Notes

Documentation, descriptions and setup brought up to date with running every workflow under a single swamp serve (2026-11-05).

03Behaviors1
@aaronge/can-i-hang-my-washing-outv2026.10.01.1washing.ts

Global Arguments

ArgumentTypeDescription
latitude?coerce.numberDefault latitude. Omit (and omit longitude) to auto-detect via IP geolocation at run time.
longitude?coerce.numberDefault longitude. Omit (and omit latitude) to auto-detect via IP geolocation at run time.
fn forecast(latitude?: coerce.number, longitude?: coerce.number)
Fetch today's forecast and score morning/afternoon washing-drying conditions
ArgumentTypeDescription
latitude?coerce.numberOverride the default latitude for this run only.
longitude?coerce.numberOverride the default longitude for this run only.

Resources

forecast(7d)— Morning/afternoon washing-drying forecast and score
04Workflows1
@aaronge/washing-forecast74416d70-e483-4b4c-8b83-caef7e88ab36

Fetches and scores today's washing-drying forecast, then exports the scores as a Prometheus textfile metric. Ships in the package and is scheduled by `swamp serve` through trigger.schedule — four times a day, 06:00 and 09:00 across the morning window, 12:00 and 17:00 across the afternoon/evening window. One forecast pass scores both windows, so the four firings just keep the data fresh. The export job replaces the tail of the old run-via-serve.sh wrapper (removed 2026-11-05); it only depends on

mainFetch and score today's washing-drying forecast
1.forecastwashing.forecast— Fetch the forecast and score morning/afternoon drying conditions
exportWrite /var/lib/prometheus/node-exporter/can-i-hang-my-washing-out.prom for the fun-stuff Grafana dashboard. Written atomically (tmp file + mv) since node_exporter may be scraping the textfile directory concurrently. The best period and the 1/0 answer (best score >= 6) are computed in CEL, so the shell only prints.
1.writeTextfile
05Previous Versions4
2026.11.05.1

Ship the workflow in the package so a single ops repo can pull it and run it under swamp serve's own scheduler.

Added 1 workflows. updated platforms

2026.10.01.1
2026.09.22.2
2026.09.22.1
06Stats
B
87 / 100
Downloads
33
Archive size
12.0 KB
  • Has README or module doc2/2earned
  • README has a code example1/1earned
  • README is substantive1/1earned
  • Most symbols documented1/1earned
  • No slow types (deprecated)1/1earned
  • Dependencies pass trust audit2/2earned
  • Docs keep secrets in a vault0/1missing
    • files/README.md--Line 77 passes the secret's value to `swamp vault put` on the command line, where shell history keeps it. Keep secrets in a vault: store them with `swamp vault put <vault> <key>`, which prompts for the value, and reference them as `${{ vault.get(<vault>, <key>) }}`.
    • files/README.md--Line 78 passes the secret's value to `swamp vault put` on the command line, where shell history keeps it. Keep secrets in a vault: store them with `swamp vault put <vault> <key>`, which prompts for the value, and reference them as `${{ vault.get(<vault>, <key>) }}`.

    Fix or accept each secret-unsafe-docs warning: the README, the manifest description and describe strings should store secrets with `swamp vault put <vault> <key>` (it prompts for the value) and pass them as `${{ vault.get(<vault>, <key>) }}`.

  • Has description1/1earned
  • Platform support declared (or universal)2/2earned
  • License1/2partial

    no SPDX license declared

  • Verified public repository2/2earned
07Platforms