These are chat archives for nightscout/beta

13th
Aug 2014
Tyler Rhodes
@trhodeos
Aug 13 2014 00:53
@bewest I created a prototype of a 'stats logging' service. Right now it pushes it out to google analytics (because it's free). But this (or something like this), would give us insight into which forks people are using, what revisions they are on (and a unique id, based on their app's hostname)
it requires that the .git directory is in the deployed app's directory, and that git is installed.. This may be a deal breaker. not sure how PaaS's handle that.
oh, and it will log any client side errors that happen
Jason Calabrese
@jasoncalabrese
Aug 13 2014 02:51
@trhodeos I think that won't work Azure, remember that the .git directory isn't available to the app, we wanted to use that to display the commit id in the settings area
but we could still get usage info
Rajat Gupta
@rajatgupta431
Aug 13 2014 06:16
@trhodeos , to add auto-restart thing on heroku , I recently started deploying using forever module . If the Procfile is set to start the web process as web: forever server.js" instead of "web: node server.js" , the results are better . And thanks for the auto deploy article link
Jason Calabrese
@jasoncalabrese
Aug 13 2014 06:25
@rajatgupta431 would something extra need to be installed for that, have you looked into setting up codeship with the heroku 1 click deploy
Rajat Gupta
@rajatgupta431
Aug 13 2014 06:30
@jasoncalabrese , forever is just a module, can be installed with npm install forever and then added to the procfile to start the web process
Jason Calabrese
@jasoncalabrese
Aug 13 2014 07:42
sounds like we should add that, maybe at the same time we integrate codeship
Ben West
@bewest
Aug 13 2014 20:03
azure can be made to work
see tblobaum/git-rev#8
Ben West
@bewest
Aug 13 2014 20:08
:+1 on forever

:+1: on forever.js https://github.com/nodejitsu/forever

npm install --save forever procfile: web: ./node_modules/.bin/forever server.js