gordonmangum / deepstream

Other
1 stars 2 forks source link

Building from scratch throws error on settings.json #3

Open sudheesh001 opened 7 years ago

sudheesh001 commented 7 years ago

Hey @gordonmangum

I've been trying to build the application. After having the required dependencies there are a few errors that prevent the application to startup. Here is the error that I receive. Is there a missing settings.json file?

   While preparing to run:
   settings.json: file not found (settings file)

Also on a side note, I was wondering, I don't think it's a good idea to push the node_modules/* directory, i've had a small issue setting things up, deleting this folder and fetching it back by doing npm install seems like a better idea, that also means that the package.json needs to be modified to follow the standard format that we get from npm init in the deepstream directory to make it look more as follows:

{
  "name": "deepstream",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "directories": {
    "lib": "lib"
  },
  "scripts": {
    "test": ""
  },
  "repository": {
    "type": "git",
    "url": "git+https://github.com/gordonmangum/deepstream.git"
  },
  "keywords": [
    "deepstream"
  ],
  "author": "Gordon Magnum <youremail@domain> (website-url)",
  "license": "MIT",
  "bugs": {
    "url": "https://github.com/gordonmangum/deepstream/issues"
  },
  "homepage": "https://github.com/gordonmangum/deepstream#readme",
  "dependencies": {
    "cheerio": "^1.0.0-rc.2",
    "elasticsearch": "^13.3.1",
    "keen-js": "^4.3.0",
    "mailchimp": "^1.2.0",
    "prerender-node": "^2.7.4",
    "twit": "^2.2.9",
    "url": "^0.11.0",
    "vimeo-api": "^1.1.5"
  }
}

I would love to help 😄

gordonmangum commented 7 years ago

Hi @sudheesh001, thanks for trying out Deepstream. We've moved the official/permanent home for this project to here: https://github.com/mitmedialab/deepstream-1 so if you could report your issue on that repo it would be better. I'll be taking this one offline eventually. Second, let me bring @dwanderton into the conversation, as he was the lead developer for a good portion of the project and may have a quick answer before I look into it.