-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
upstart script for running with nodeenv #124
Comments
Maybe just use a node.js specific way to keep the process alive? https://github.com/nodejitsu/forever is a common solution. |
To be exactly, I've already tried that (inside an Upstart script, according to https://www.exratione.com/2013/02/nodejs-and-forever-as-a-service-simple-upstart-and-init-scripts-for-ubuntu/). But that is an additional layer of complexity that I didn't get to work. It's all a little hacky, but running now with: cd /var/www/tilestream
. tilestream_env/bin/activate
sudo npm install
sudo forever start ./index.js --config config.json Any plans to upgrade tilestream to newer node versions in the future? Thanks! |
It works with node v0.10.x in master if that is what you mean? Are you building from the master github repo? |
Sure, I am using the version from github master. |
I am trying to run tilestream on an Ubuntu 12.04 server with nodeenv according to the instructions on the Readme.
Sadly, I'm stuck at configuring the Upstart script accordingly. Running Tilestream from the command line works so far.
Can you provide more detailed information on the Readme or an Upstart configuration example?
The text was updated successfully, but these errors were encountered: