'docker-compose up' doesn't work.

[luketainton]

See log below.

Attaching to mesahub_mongodata_1, mesahub_web_1, mesahub_mongo_1 mesahub_mongodata_1 exited with code 0 mongo_1 | 2018-01-17T17:12:04.157+0000 I CONTROL [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=9bb3db601e25 mongo_1 | 2018-01-17T17:12:04.157+0000 I CONTROL [initandlisten] db version v3.6.2 mongo_1 | 2018-01-17T17:12:04.157+0000 I CONTROL [initandlisten] git version: 489d177dbd0f0420a8ca04d39fd78d0a2c539420 mongo_1 | 2018-01-17T17:12:04.157+0000 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.1t 3 May 2016 mongo_1 | 2018-01-17T17:12:04.157+0000 I CONTROL [initandlisten] allocator: tcmalloc mongo_1 | 2018-01-17T17:12:04.157+0000 I CONTROL [initandlisten] modules: none mongo_1 | 2018-01-17T17:12:04.157+0000 I CONTROL [initandlisten] build environment: mongo_1 | 2018-01-17T17:12:04.157+0000 I CONTROL [initandlisten] distmod: debian81 mongo_1 | 2018-01-17T17:12:04.157+0000 I CONTROL [initandlisten] distarch: x86_64 mongo_1 | 2018-01-17T17:12:04.157+0000 I CONTROL [initandlisten] target_arch: x86_64 mongo_1 | 2018-01-17T17:12:04.157+0000 I CONTROL [initandlisten] options: { net: { bindIpAll: true } } mongo_1 | 2018-01-17T17:12:04.158+0000 I - [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'. mongo_1 | 2018-01-17T17:12:04.158+0000 I STORAGE [initandlisten] mongo_1 | 2018-01-17T17:12:04.158+0000 I STORAGE [initandlisten] WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine mongo_1 | 2018-01-17T17:12:04.158+0000 I STORAGE [initandlisten] See http://dochub.mongodb.org/core/prodnotes-filesystem mongo_1 | 2018-01-17T17:12:04.158+0000 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=3403M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=(recovery_progress), mongo_1 | 2018-01-17T17:12:04.290+0000 I STORAGE [initandlisten] WiredTiger message [1516209124:290317][1:0x7f22b994fa00], txn-recover: Main recovery loop: starting at 6/4736 web_1 | web_1 | > mesahub@0.2.0 start /app web_1 | > node ./bin/www web_1 | web_1 | module.js:471 web_1 | throw err; web_1 | ^ web_1 | web_1 | Error: Cannot find module 'express' web_1 | at Function.Module._resolveFilename (module.js:469:15) web_1 | at Function.Module._load (module.js:417:25) web_1 | at Module.require (module.js:497:17) web_1 | at require (internal/module.js:20:19) web_1 | at Object. (/app/main.js:1:77) web_1 | at Module._compile (module.js:570:32) web_1 | at Object.Module._extensions..js (module.js:579:10) web_1 | at Module.load (module.js:487:32) web_1 | at tryModuleLoad (module.js:446:12) web_1 | at Function.Module._load (module.js:438:3) web_1 | web_1 | npm ERR! Linux 4.13.0-25-generic web_1 | npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start" web_1 | npm ERR! node v6.12.3 web_1 | npm ERR! npm v3.10.10 web_1 | npm ERR! code ELIFECYCLE web_1 | npm ERR! mesahub@0.2.0 start: node ./bin/www web_1 | npm ERR! Exit status 1 web_1 | npm ERR! web_1 | npm ERR! Failed at the mesahub@0.2.0 start script 'node ./bin/www'. web_1 | npm ERR! Make sure you have the latest version of node.js and npm installed. web_1 | npm ERR! If you do, this is most likely a problem with the mesahub package, web_1 | npm ERR! not with npm itself. web_1 | npm ERR! Tell the author that this fails on your system: web_1 | npm ERR! node ./bin/www web_1 | npm ERR! You can get information on how to open an issue for this project with: web_1 | npm ERR! npm bugs mesahub web_1 | npm ERR! Or if that isn't available, you can get their info via: web_1 | npm ERR! npm owner ls mesahub web_1 | npm ERR! There is likely additional logging output above. web_1 | npm WARN Local package.json exists, but node_modules missing, did you mean to install? web_1 | web_1 | npm ERR! Please include the following file with any support request: web_1 | npm ERR! /app/npm-debug.log mongo_1 | 2018-01-17T17:12:04.387+0000 I STORAGE [initandlisten] WiredTiger message [1516209124:387856][1:0x7f22b994fa00], txn-recover: Recovering log 6 through 7 mongo_1 | 2018-01-17T17:12:04.442+0000 I STORAGE [initandlisten] WiredTiger message [1516209124:442863][1:0x7f22b994fa00], txn-recover: Recovering log 7 through 7 mongo_1 | 2018-01-17T17:12:04.532+0000 I CONTROL [initandlisten] mongo_1 | 2018-01-17T17:12:04.532+0000 I CONTROL [initandlisten] WARNING: Access control is not enabled for the database. mongo_1 | 2018-01-17T17:12:04.532+0000 I CONTROL [initandlisten] Read and write access to data and configuration is unrestricted. mongo_1 | 2018-01-17T17:12:04.532+0000 I CONTROL [initandlisten] mongo_1 | 2018-01-17T17:12:04.548+0000 I FTDC [initandlisten] Initializing full-time diagnostic data capture with directory '/data/db/diagnostic.data' mongo_1 | 2018-01-17T17:12:04.549+0000 I NETWORK [initandlisten] waiting for connections on port 27017 mesahub_web_1 exited with code 1 

[PandelisZ]

---Need to do npm install before launching---

EDit: fake news that's not the issue

[PandelisZ]

Ah okay i remember there being an issue with the binary versions of npm modules. Would have to change this to build the node modules in the docker :/ HMMMMMm

[luketainton]

I did do npm install, then I got this log.

[PandelisZ]

It works fine for me if i comment out the twilio line btw:

from texting.js // const client = require('twilio')(accountSid, authToken);

[luketainton]

I'll try it later

---

From: Pandelis Zembashis notifications@github.com Sent: Thursday, January 18, 2018 4:37:26 PM To: HaCSBCU/MesaHub Cc: Luke Tainton; Author Subject: Re: [HaCSBCU/MesaHub] 'docker-compose up' doesn't work. (#69)

It works fine for me if i comment out the twilio line btw:

from texting.js // const client = require('twilio')(accountSid, authToken);

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/HaCSBCU/MesaHub/issues/69#issuecomment-358703881, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AVhDsYjwKWfd0r78BFMkcI1NyJnEsz0Qks5tL3NGgaJpZM4RhrsC.

[PandelisZ]

Ok theres a number of issues with running the docker. Cause its expecting to read from some postgresql data.

We need to have a discord chat about it. Tomorrow?

It probly needs like a couple of hours of work added to it and some seeding of the initial DB

[luketainton]

Sure, any time after 3:30pm is good 😊

[seenaomi]

So is this still an issue then? I am interested in checking this project out.

[PandelisZ]

Hi @seenaomi,

There was a big change in the way we architected the project, we went from mongo to postgresql and the docker enviroment never switched over.

You can run it outside of docker if you have a postgresql server you can point it to. It could definately use some work to make the process easier to setup but we never had the time to put into doing that.

[PandelisZ]

Ok so i've actually finally fixed this in #72