Closed ungoldman closed 8 years ago
i took a look at this today, and even after referencing an IN_MEMORY cache and confirming that the app runs fine on my local machine, i can confirm that a heroku instance crashes immediately, which is strange because it used to just work™
i created a branch, but the logs are pretty uninformative so i'm going to have to chew on this to try and figure out what to do next.
nm: i made a few more tweaks (including renaming index.js
to > server.js
and finally have a working push button deployment.
https://fast-springs-50571.herokuapp.com/github/chelm/grunt-geo/forks
why would renaming index.js to server.js make a difference? package.json points to index.js afaict
i changed the command associated with npm start too because i saw an error in a heroku log that 'server.js couldn't be found'.
seems weird to me. i would expect either to work. but out of 4 deployments, only fast-springs
is spitting back .geojson.
weird. I'm guessing a lot has changed since I was kooping. thanks for staying on it @jgravois
:star: :star: :star: :star: :star:
log:
There's no database there so it falls down right away. Might be better to either use local cache out of the box, or to provide specific instructions on connecting koop to a Heroku Postgres database with PostGIS enabled (still experimental).