koopjs / koop-provider-example Goto Github PK

Hi
this repo is pinned at https://github.com/koopjs page, but it is deprecated.
What about switching the pin to the koop-provider?
Regards
Arnaud

Version 1.29.1 of config was just published.

This version is covered by your current version range and after updating it in your project the build failed.

config is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 2.84.0 of request was just published.

This version is covered by your current version range and after updating it in your project the build failed.

request is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml
• Replaced the old Node.js version in your .nvmrc with the new one

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

i tried spinning up a local koop instance using this sample yesterday afternoon and didn't have much joy

STR

1. downloaded ZIP

npm install
node server.js
..
>>cannot find 'koop-osm' / cannot find 'koop-tile-plugin dependencies'

1. added the following to the package.json

"koop-osm": "~0.0.5",
"koop-tile-plugin": "~1.0.0"

1. blew away node_modules folder and reran npm install
2. reran node server.js

body-parser deprecated bodyParser: use individual json/urlencoded middlewares node_modules/koop/index.js:19:11
body-parser deprecated undefined extended: provide extended option node_modules/koop/node_modules/body-parser/index.js:85:29
No Github Token in config. This may cause problems accessing data.
No Github Token in config. This may cause problems accessing data.
Listening at http://0.0.0.0:1337/

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED
    at RedisClient.on_error (/Users/john6251/Downloads/koop-sample-app-master/node_modules/koop/node_modules/kue/node_modules/redis/index.js:196:24)
    at Socket.<anonymous> (/Users/john6251/Downloads/koop-sample-app-master/node_modules/koop/node_modules/kue/node_modules/redis/index.js:106:14)
    at Socket.emit (events.js:95:17)
    at net.js:441:14
    at process._tickDomainCallback (node.js:486:13)

not sure what i'm missing. originally i thought i'd just borked my Postgres instance, but i fixed it this morning and the behavior's the same.

Has anyone tried using the sample to deploy to AWS Lambda lately? It fails on the "npm run lambda-create". At least for me. Anyone have success?

The dependency config was updated from 3.0.0 to 3.0.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

config is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

sorry for the issue only tangentially related to this repo.

i think having some authoritative documentation (particularly on existing providers) to link to would make keeping the doc up to date a lot more realistic than having content peppered throughout individual repos.

• are things like the wiki providers doc we created before worth preserving?
• alternatively, perhaps we should be thinking about a wiki or dedicated documentation repo within koopjs?