* For now, drop mapbox for OSM tiles
* For now, drop mapbox for OSM tiles
* Use OSM tiles
* Remove mapbox secrets for now. If we bring back mapbox; we should re-enstate
* Only show up to 200 plantings
* Update app/assets/javascripts/members.js.erb
* [CodeFactor] Apply fixes
* Update production.rb
---------
Co-authored-by: codefactor-io <support@codefactor.io>
* For now, drop mapbox for OSM tiles
* For now, drop mapbox for OSM tiles
* Use OSM tiles
* Remove mapbox secrets for now. If we bring back mapbox; we should re-enstate
* Update members.js.erb
* Change placeholder
on both crops and places pages
Did this because the clusters were annoyingly over-general, eg. showing
164 people in the eastern part of North America. Cluster radius of 20px
is about the radius of the cluster icon itself. Seems to work better
eg. for separating Melbourne from Sydney on the world map.
When we tried to deploy maps on staging, we got the following error
message in our Javascript console:
Error: Couldn't autodetect L.Icon.Default.imagePath, set it manually.
... so we did. The end.
Ugh, I know. But it's not any less secure than having it out there in
our Javascript, and it turns out Heroku just downright *refuses* to read
it from an environment variable during asset compilation. I even tried
an experimental Heroku addon
(https://devcenter.heroku.com/articles/labs-user-env-compile) but it
didn't work, so for now let's just do this and get it out there. I'm
sick of messing with it.