You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
EDIT: Submitted by mistake before writing a message.
I'm using NodeBB on Heroku and I need S3 for all the file uploads. I installed the plugin using npm and then pushed the directory back up to Heroku. I'm configuring everything as environment variables, so access key, secret key, host and bucket are all defined in the Heroku control panel. As I understand, path would be set by default to /.
At the moment I'm getting two errors, one on the console:
warn: [plugins/nodebb-plugin-s3-uploads-updated] Mapped path 's3 => /app/node_modules/nodebb-plugin-s3-uploads-updated/public' not found.
And one on the admin control panel:
Internal error.
Oops! Looks like something went wrong!
/api/admin/plugins/s3-uploads
Cannot find module './../../config.json'
This second one might be the issue here, as I have no config.json on the server. All variables for NodeBB configuration are also defined as environment variables.
The text was updated successfully, but these errors were encountered:
jcano
changed the title
Error messages when deploying on Heroku with evironment variables
Using the plugin with no config.json
Aug 3, 2016
EDIT: Submitted by mistake before writing a message.
I'm using NodeBB on Heroku and I need S3 for all the file uploads. I installed the plugin using
npm
and then pushed the directory back up to Heroku. I'm configuring everything as environment variables, so access key, secret key, host and bucket are all defined in the Heroku control panel. As I understand, path would be set by default to/
.At the moment I'm getting two errors, one on the console:
And one on the admin control panel:
This second one might be the issue here, as I have no
config.json
on the server. All variables for NodeBB configuration are also defined as environment variables.The text was updated successfully, but these errors were encountered: