Problems with Heroku, Geodjango and Couchbase? Me too!
Today it was a long day.
I started by wanting to create a simple service that is going to run on heroku, store some tweets according to some specific keywords that a user is going to type and then provide some trends regarding those.
Piece of cake actually, until Heroku started the annoying stuff.
My selection for storing the tweets was Couchbase. It is a really advanced NoSQL database, allowing scaling and many many other interesting facts that anyone playing with big data would love.
The problem is, that Heroku does not allow couchbase client libraries to compile on its stack.
For that reason i started creating my own buildpack here, https://github.com/mpetyx/heroku-buildpack-couchbase-geo-django.
As you can see, it contains also the popular GeoDjango library. It needs no recommendations, as most of the django developers playing with geospatial data use it.
It is a pity that Heroku does not offer a default choice to actually include that library in your app's venv.
Currently I have fixed the GeoDjango in a stable format and tomorrow hopefully i will upload the rest.
I am so tired to continue and conclude now.
Regards,
Michael.
I started by wanting to create a simple service that is going to run on heroku, store some tweets according to some specific keywords that a user is going to type and then provide some trends regarding those.
Piece of cake actually, until Heroku started the annoying stuff.
My selection for storing the tweets was Couchbase. It is a really advanced NoSQL database, allowing scaling and many many other interesting facts that anyone playing with big data would love.
The problem is, that Heroku does not allow couchbase client libraries to compile on its stack.
For that reason i started creating my own buildpack here, https://github.com/mpetyx/heroku-buildpack-couchbase-geo-django.
As you can see, it contains also the popular GeoDjango library. It needs no recommendations, as most of the django developers playing with geospatial data use it.
It is a pity that Heroku does not offer a default choice to actually include that library in your app's venv.
Currently I have fixed the GeoDjango in a stable format and tomorrow hopefully i will upload the rest.
I am so tired to continue and conclude now.
Regards,
Michael.
Σχόλια
Δημοσίευση σχολίου