No description
Find a file
2026-03-30 16:36:34 +02:00
.env.example washinima init 2026-03-29 23:07:52 +02:00
.gitignore washinima init 2026-03-29 23:07:52 +02:00
compose.yml washinima init 2026-03-29 23:07:52 +02:00
deno.json washinima init 2026-03-29 23:07:52 +02:00
deno.lock washinima init 2026-03-29 23:07:52 +02:00
Dockerfile washinima init 2026-03-29 23:07:52 +02:00
LICENSE washinima init 2026-03-29 23:07:52 +02:00
machines.ts washinima init 2026-03-29 23:07:52 +02:00
main.ts add deadman switch 2026-03-30 16:36:34 +02:00
README.md washinima init 2026-03-29 23:07:52 +02:00
shell.nix washinima init 2026-03-29 23:07:52 +02:00

Washinima

Checking every 30 seconds for a laundry station on one of WashNet's Laundrettes? Get notified instead!

Development

Set-up your development environment with nix-shell.

Deployment

  1. Clone the repository.
  2. Copy .env.example to .env and change the respective environment variables
    • You can get the WashNet AJAX URL by exploring the XHR/Fetch requests of your Laundrette's status page. There will be a GET request to /ajax_controller/displayMachines/.../en, that is the URL you are looking for.
    • You can replace washnet-api-provider.example with the hostname of your provider.
  3. Run docker compose up -d to start the container.
  4. Subscribe to the ntfy topic you set in the .env file.
    • Avoid predictable or common topic names. You can generate a random topic name with the following command: echo "washinima_$(od -vN 16 -An -tx1 /dev/urandom | tr -d ' \n' | head -c 12)"

Disclaimer This Software obtains information from services with a WashNet-compatible API. Check the Terms of Service of your WashNet-compatible API provider before using it. You are solely responsible for ensuring your use complies with any applicable terms. Without prejudice to the Software's license, you accept full responsibility for any consequences.