Setup issues
See original GitHub issueI didn’t see this in the readme and I think it could be useful to others. I followed your setup instructions on a fresh Ubuntu box, and besides a few dependency problems (the sqlite version was incompatible with the node version), the only real problem I have is that the server doesn’t stay “online”. I don’t know if you have a recommendation for this but if you have any tips on how to get this to stay up I’d love to hear it. I don’t know if maybe I did something wrong, maybe I need to set up some kind of uptime daemon, or what, but I constantly have to ssh into the box and run node index
to start the server up again. Also, it defaulted to port 5000 and I couldn’t find in the readme where to change this default port. Any tips for these 2 issues?
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (1 by maintainers)
To answer your first two questions.
In index.js the last section:
app.listen(5000 || process.env.PORT, function(){ console.log(“The magic is happening on port 5000”);
You can change the port there.
I use pm2 to keep my application live 😃
Hope it helps
Dan
@BanshaTang The “Pool is destroyed” error occurs when the app faces some trouble connecting/interacting with the database. Does the user running the app has write access to the
db
directory? Please check permissions and let me know.Edit: So I see you’ve created a separate issue for this. Let’s move this conversation there.