@Neeru-Gupta We tried using the same plugin,nodebb-plugin-fusionauth-oidc for authenticating through the keycloak provider but While rebuilding & restarting after installing our Nodebb app breaks. We are unable to proceed further. We have to again clone the whole code to get started with.
Could you please share with me the steps on how you have done & configured it?
We are using another plugin now as nodebb-plugin-sso-oidc which we are able to install & configure. But we are getting SSL protocol error while trying to login
nodebb 1.6.1 on heroku
-
Has anyone successfully deployed nodebb v1.6.1 + mongodb on heroku ?
I am getting below errors on heroku
Steps ---
git clone -b v1.6.1 https://github.com/NodeBB/NodeBB.git nodebb
cd nodebb
npm install
node app --setup
echo 'web: node loader.js --no-daemon' > Procfile
git add -f Procfile config.json package.json build loader.js && git commit -am "adding Procfile and configs for Heroku"
git push heroku masterLogs---
2017-11-13T17:06:16.000000+00:00 app[api]: Build succeeded
2017-11-13T17:07:04.004170+00:00 heroku[web.1]: Starting process with commandnode loader.js --no-daemon
2017-11-13T17:07:06.592423+00:00 app[web.1]: module.js:544
2017-11-13T17:07:06.592435+00:00 app[web.1]: throw err;
2017-11-13T17:07:06.592436+00:00 app[web.1]: ^
2017-11-13T17:07:06.592437+00:00 app[web.1]:
2017-11-13T17:07:06.592437+00:00 app[web.1]: Error: Cannot find module './src/file'
2017-11-13T17:07:06.592438+00:00 app[web.1]: at Function.Module._resolveFilename (module.js:542:15)
2017-11-13T17:07:06.592439+00:00 app[web.1]: at Function.Module._load (module.js:472:25)
2017-11-13T17:07:06.592439+00:00 app[web.1]: at Module.require (module.js:585:17)
2017-11-13T17:07:06.592440+00:00 app[web.1]: at require (internal/module.js:11:18)
2017-11-13T17:07:06.592441+00:00 app[web.1]: at Object.<anonymous> (/app/loader.js:11:12)
2017-11-13T17:07:06.592441+00:00 app[web.1]: at Module._compile (module.js:641:30)
2017-11-13T17:07:06.592442+00:00 app[web.1]: at Object.Module._extensions..js (module.js:652:10)
2017-11-13T17:07:06.592442+00:00 app[web.1]: at Module.load (module.js:560:32)
2017-11-13T17:07:06.592443+00:00 app[web.1]: at tryModuleLoad (module.js:503:12)
2017-11-13T17:07:06.592444+00:00 app[web.1]: at Function.Module._load (module.js:495:3)
2017-11-13T17:07:06.757409+00:00 heroku[web.1]: State changed from starting to crashed
2017-11-13T17:07:06.760518+00:00 heroku[web.1]: State changed from crashed to starting
2017-11-13T17:07:06.679819+00:00 heroku[web.1]: Process exited with status 1
2017-11-13T17:07:12.412941+00:00 heroku[web.1]: Starting process with commandnode loader.js --no-daemon
2017-11-13T17:07:14.670348+00:00 app[web.1]: module.js:544
2017-11-13T17:07:14.670364+00:00 app[web.1]: throw err;
2017-11-13T17:07:14.670365+00:00 app[web.1]: ^
2017-11-13T17:07:14.670365+00:00 app[web.1]:
2017-11-13T17:07:14.670366+00:00 app[web.1]: Error: Cannot find module './src/file'
2017-11-13T17:07:14.670367+00:00 app[web.1]: at Function.Module._resolveFilename (module.js:542:15)
2017-11-13T17:07:14.670368+00:00 app[web.1]: at Function.Module._load (module.js:472:25)
2017-11-13T17:07:14.670368+00:00 app[web.1]: at Module.require (module.js:585:17)
2017-11-13T17:07:14.670369+00:00 app[web.1]: at require (internal/module.js:11:18)
2017-11-13T17:07:14.670370+00:00 app[web.1]: at Object.<anonymous> (/app/loader.js:11:12)
2017-11-13T17:07:14.670370+00:00 app[web.1]: at Module._compile (module.js:641:30)
2017-11-13T17:07:14.670371+00:00 app[web.1]: at Object.Module._extensions..js (module.js:652:10)
2017-11-13T17:07:14.670371+00:00 app[web.1]: at Module.load (module.js:560:32)
2017-11-13T17:07:14.670372+00:00 app[web.1]: at tryModuleLoad (module.js:503:12)
2017-11-13T17:07:14.670373+00:00 app[web.1]: at Function.Module._load (module.js:495:3)
2017-11-13T17:07:14.743570+00:00 heroku[web.1]: Process exited with status 1
2017-11-13T17:07:14.770746+00:00 heroku[web.1]: State changed from starting to crashed -
Seems like
loader.js
might not be executed in the correct directory. Is there a way to set the working directory? -
I was able to get around it by pushing all files to heroku git instead of mentioned files in documentations
So, instead of,
git add -f Procfile config.json package.json build && git commit -am "adding Procfile and configs for Heroku"
I did,
git add . && git commit -am "adding Procfile and configs for Heroku"This solved my problem.
However, I have moved away from Heroku and deployed my forum on GCP.