We really ought to transition it over to our SaaS services. Where do I send the bill?
And where will users find you if, god forbid something goes down? All eggs one basket and all that...
Also make sure redis is running. Try
redis-cli in console to see if you can get in.
Hmmm...can't get in. Here's what happened:
| $ redis-cli
| Could not connect to Redis at 127.0.0.1:6379: Connection refused
| not connected>
I think I just don't have Redis set up properly. I'll work on that. But now I'm wondering--should I be using Redis in the first place? I am creating a forum to host on AWS and the database needs to support svg, pdf, and png filetypes. Is Redis the right option? If not, what are my options?
Thanks for all the help!
NodeBB doesn't store files in the database, it will store images and files locally or images on imgur if you provide a imgur clientID in admin panel. We will add s3 storage support too.
Do you have any suggestions for using this software to host a forum on AWS? I'm not clear on where everything would be stored...
You would just create an EC2 instance and install all dependencies and then install NodeBB. That should work fine. After that you can either add a imgur client ID so that all images are uploaded to imgur or enable local file uploads. When local file uploads are enabled all the files go to the /public folder in the NodeBB installation folder. Obviously its more preferable to have S3 support so you can store files there.
Thanks for the overview!
Now I'm trying to run the project. I got redis set up. I managed to start the server the first few times I tried it, but then the next time, I got this result:
 13 Jan 17:46:33.969 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
 13 Jan 17:46:33.971 * Max number of open files set to 10032
 13 Jan 17:46:33.972 # Creating Server TCP listening socket *:6379: bind: Address already in use
Additionally, even when I got the server to run, when I did "npm install" and then "node app.js," I got an error saying bcrypt wasn't installed even though I had listed it as a dependency.
Any ideas on how to solve these issues? Thanks!
Okay, I figured out how to shutdown the redis instance so ignore the top part of my last question.
But I am still having issues with bcrypt. The readout when I do "npm install" says there's a problem with bcrypt itself and you can see what happens when I try running the code. How do I get around this?
$ node app.js
info: NodeBB v0.2.1 Copyright (C) 2013 DesignCreatePlay Inc.
info: This program comes with ABSOLUTELY NO WARRANTY.
info: This is free software, and you are welcome to redistribute it under certain conditions.
info: Initializing NodeBB v0.2.1, on port 4567, using redis store at 127.0.0.1:6379.
info: NodeBB instance bound to: Any address (0.0.0.0)
warn: Couldn't find convert. Did you install imagemagick?
Error: Cannot find module 'bcrypt'
at Function.Module._resolveFilename (module.js:331:15)
at Function.Module._load (module.js:273:25)
at Module.require (module.js:357:17)
at require (module.js:373:17)
at Object.<anonymous> (/Users/aaronclaytondunn/Documents/WebDev/nodebb/nodebb1/nodebb/src/user.js:1:76)
at Module._compile (module.js:449:26)
at Object.Module._extensions..js (module.js:467:10)
at Module.load (module.js:349:32)
at Function.Module._load (module.js:305:12)
at Module.require (module.js:357:17)
CentOS users have also reported problems installing bcrypt.
Try installing this instead, and let us know if it works?
Thank you, that worked.
When you update it, you'll have to do this fix as well: https://github.com/shaneGirish/bcrypt-nodejs/issues/11