Automatic bonus point spender for MyAnonamouse. Runs as a lightweight Docker container (~15 MB) with a web dashboard for configuration and monitoring.

Forager converts idle bonus points into upload credit on a schedule, keeping your ratio healthy without manual intervention. It can also maintain VIP membership, buy Freeleech Wedges, and contribute to the Millionaire's Vault.

• Upload Credit — Buy upload in bulk (500 pts/GB, 50 GB minimum per purchase)
• VIP Top-Off — Automatically extend VIP to the 90-day cap when it drops below threshold
• Freeleech Wedges — Buy wedges at 50,000 pts each (before upload, or wedge-only mode)
• Millionaire's Vault — Donate 2,000 pts per pot (once per pot or daily)
• Spend Preview — Next Spend card shows a live simulation based on current stats and settings
• Spend History — Rolling 90-day log of all purchases
• Points/Hour — Live stats scraped from your profile page
• Pause/Resume — Temporarily halt scheduled spending
• Auto-Refresh — Configurable refresh interval (default 5 min) fetches live stats from MAM
• Dark UI — Single-page dashboard with collapsible cards

# docker-compose.yml
services:
  forager:
    build: ./forager
    container_name: forager
    environment:
      - TZ=America/Los_Angeles
    env_file:
      - ./forager/settings.env
    ports:
      - "127.0.0.1:5011:5011"
    volumes:
      - ./forager:/srv/forager
    restart: always
    healthcheck:
      test: ["CMD-SHELL", "curl -fs http://localhost:5011/health || exit 1"]
      interval: 30s
      timeout: 10s
      retries: 3

docker-compose up -d forager

Open http://localhost:5011 and paste your mam_id cookie to get started.

1. Log in to MAM in your browser
2. Go to Settings → Security → scroll to mam_id
3. Copy the value and paste it into the Forager UI under Cookie

That's all you need for core functionality (upload credit, VIP, wedges).

Vault donations require a browser session cookie (mbsc) and User-Agent string because the vault pages don't support the JSON API.

1. Open MAM in Chrome and navigate to any page
2. Open DevTools → Application → Cookies → myanonamouse.net
3. Copy the mbsc cookie value
4. Copy your browser's User-Agent string (DevTools → Console → navigator.userAgent)
5. Paste both into the Forager UI under Browser Session

The session is self-sustaining — Forager captures the rotated cookie from each response and keeps the session alive with periodic page loads every 4 hours.

All runtime settings are managed through the web UI and stored in state.json. No container restart needed.

Set in settings.env:

Each cycle (scheduled or manual) runs this sequence:

1. Fetch profile from MAM API — current points, VIP expiry, upload/download stats
2. VIP top-off — if enabled and VIP is more than 1 day below the 90-day cap, buy days to reach the cap (~178.57 pts/day)
3. Wedge purchase — if enabled and points exceed buffer + 50,000
4. Vault donation — if enabled, browser session is active, and contribution conditions are met (once per pot or daily)
5. Upload purchase — spend remaining points above buffer on upload credit (single purchase, 50 GB minimum)
6. Verify — re-fetch profile to confirm purchases succeeded
7. Record — save spend details to history and update lifetime totals

Forager uses two separate authentication mechanisms:

• mam_id cookie — for the JSON API (/jsonLoad.php, /json/bonusBuy.php). Used for all point spending and profile queries. Obtained from MAM account settings.
• mbsc cookie — for HTML pages (vault, profile page). Rotates on every request. Required only for vault features and points/hour stats.

All endpoints return JSON with CORS headers.

forager/
├── Dockerfile              Alpine 3.21 + curl + jq + lighttpd
├── VERSION                 Semantic version string
├── settings.env            Environment variables (auth, port)
├── app/
│   ├── entrypoint.sh       Process supervisor (lighttpd + spender)
│   ├── lib.sh              Shared library (MAM API, state, spending logic)
│   ├── spender.sh          Background daemon (scheduled spends + session keepalive)
│   └── test.sh             Test suite (shunit2)
└── www/
    ├── index.html           Single-page dashboard (vanilla JS)
    └── cgi-bin/             CGI endpoints (shell scripts via lighttpd)

• No dependencies beyond Alpine base packages (curl, jq, lighttpd)
• No build step — shell scripts and vanilla JS
• Single container — lighttpd serves both the SPA and CGI endpoints
• State on disk — state.json persists via volume mount at /srv/forager

docker exec forager sh /app/test.sh

Tests cover state management, locking, timestamp formatting, and API endpoints (unit tests run against a separate lighttpd instance on a different port).

MIT