Can I Hang My Washing Out
Scores whether it's worth hanging your washing out this morning and this afternoon, from free temperature/humidity/wind/rain/sunshine forecast data.
Documentation, descriptions and setup brought up to date with running every workflow under a single swamp serve (2026-11-05).
Global Arguments
| Argument | Type | Description |
|---|---|---|
| latitude? | coerce.number | Default latitude. Omit (and omit longitude) to auto-detect via IP geolocation at run time. |
| longitude? | coerce.number | Default longitude. Omit (and omit latitude) to auto-detect via IP geolocation at run time. |
| Argument | Type | Description |
|---|---|---|
| latitude? | coerce.number | Override the default latitude for this run only. |
| longitude? | coerce.number | Override the default longitude for this run only. |
Resources
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
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
- 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