cyberdelia / heroku-geo-buildpack

Geo libraries for Heroku
https://github.com/heroku/heroku-geo-buildpack
113 stars 135 forks source link

Geos is not supported/available #23

Open benjamin-hull opened 9 years ago

benjamin-hull commented 9 years ago

This may be related to other recent issues that have come up. My Rails app on Heroku recently started erroring when any geometry based operation was attempted.

I've updated heroku-geo-buildpack, checked references, switched stack to cedar-14. The deployment and build process seems to work fine, but RGeo::Geos.supported? always returns false.

This is under Ruby 2.1.5. My .buildpacks file looks like:

https://github.com/cyberdelia/heroku-geo-buildpack.git#1.3
https://github.com/heroku/heroku-buildpack-ruby.git#v129

Here's the start of my deploy log (looks fine to me)

-----> Fetching custom git buildpack... done
-----> Multipack app detected
=====> Downloading Buildpack: https://github.com/cyberdelia/heroku-geo-buildpack.git
=====> Detected Framework: geos/gdal/proj
       Using geos version: 3.4.2
       Using gdal version: 1.11.1
       Using proj version: 4.8.0_1
-----> Vendoring geo libraries done
=====> Downloading Buildpack: https://github.com/heroku/heroku-buildpack-ruby.git
=====> Detected Framework: Ruby
-----> Compiling Ruby/Rails
-----> Using Ruby version: ruby-2.1.5

I have tried purging the repo cache, rebuilding, and many different forks of this buildpack that try to fix this issue, but it hasn't made any difference.

Are you able to suggest anything else to workaround or diagnose the issue?

Thank you!

waissbluth commented 9 years ago

Same here, but ruby 2.2.0 and cedar.

smcoll commented 9 years ago

Have you tried reversing the order of the buildpacks listed in .buildpacks? i had a similar issue, with a Python stack. It seems that the multi-buildpack uses the release configuration from the buildpack listed last.

carlosfunk commented 9 years ago

Reversing the buildpacks worked for me

allthesignals commented 9 years ago

Reversing the buildpacks didn't seem to work for me. RGeo::Geos.supported? still returns false.

jkogara commented 8 years ago

@allthesignals Did you get this to work? I've tried reversing buildpacks and purging the repo but to no avail.

allthesignals commented 8 years ago

@jkogara No luck. I had to create a custom Dockerfile to get it to work.

mgiraldo commented 8 years ago

any luck for someone else without Dockerfiles?