NYC Trash Map

Interactive map of New York City trash, recycling, organics, and bulk-item collection schedules by street and day.

  • Other
  • Tools & Utilities
Interactive map of New York City trash, recycling, organics, and bulk-item collection schedules by street and day.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

47/100 Fair

Maintained
79last commit 12 days ago
Popular
61 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 19 days ago

GitHub stars
1
Open issues
17
Last commit
2026-11-09
Latest release
v1.0.3
License
MIT
Activity
steady

Checked 6 days ago - source: GitHub (johnngone/nyc-trash-map)

Resources & Compatibility

Requirements not published yet.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Docker Install Hostable as a standalone Docker container. Copy .env.production.example to .env, replace map.example.com with your own domain, and run: docker compose --env-file .env -f compose.production.yaml up -d. The production example pulls ghcr.io/johnngone/nyc-trash-map:latest and uses Caddy-managed HTTPS with persistent data and certificate volumes. source
  • Docker Compose Install Host with Docker Compose: copy .env.production.example to .env, replace map.example.com with your own domain, then run docker compose --env-file .env -f compose.production.yaml up -d. The production example uses a Caddy reverse proxy for HTTPS and persistent data and certificate volumes. source

Fetched today - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What ports are needed for the production Docker Compose setup?

The example uses Caddy for HTTPS, so DNS for the domain must point to the host and ports 80 and 443 must reach Caddy.

Can I deploy it behind an existing reverse proxy?

Yes, run the standalone container in HTTP-only mode and publish the application port 8000 to a host port. Mount a persistent data directory and set DATA_REFRESH_ON_STARTUP=true. Set APP_PUBLIC_URL to the public HTTPS origin without a trailing slash.

What happens on first startup or first refresh?

The first refresh downloads the source data and builds the map release. The basemap can load before that work is done, and street schedules appear after the release passes validation.

How do I pin a release instead of always using latest?

The production example always pulls the latest image. Set APP_IMAGE in the .env file when you want to pin a release instead.

Can I reuse persisted data from an old installation?

The source says to start a new installation with an empty data directory. Incompatible manifests and artifacts are deliberately rejected.

Do I need to rebuild the image after changing branding variables?

Set the APP_* variables to customize visible branding and the metadata returned in the initial HTML response. Recreate the container after changing them; the image does not need to be rebuilt.

Answers sourced from github.com

Community

Collected 3 days ago - public community threads