Slacking on other free clouds? about slackin HOT 9 OPEN

I have ours deployed on Cloud Foundry (over at http://community.emccode.com), I'm sure you can find some cheap/free accounts there.

from slackin.

I think just starting a nodejs server on any cloud (AWS-FreeTier, Azure Trial, OpenShift) would be enough. Then, run npm install -g slackin; slackin <domain> <token> and you're good to go.

from slackin.

I have deployed Slackin on Openshift and it's fine. Unlike Heroku, Openshift has no hours/day limits.

from slackin.

@kumarharsh using it in this way is running, but as I log out from ssh, it stops. Is there any way to use pm2 or forever to run slackin?

from slackin.

yeah, I guess you can use something like nohup

from slackin.

Thanks @kumarharsh, at the end we used start-stop-daemon

from slackin.

@nasht00 Practically speaking, what happens when the 16-hour limit on Heroku is reached?

Does that mean that the app will reboot on the next user's request and take about 15-30 seconds to load or does it mean that the user will be out of luck and can' get in for another 8 hours?

from slackin.

@LucasCioffi it means the app will be offline for another 8 hours (if the app really was active for 16 straight hours).

By the way, my solution was Bluemix.

from slackin.

I'm working on a Deploy to Azure button at the moment over with this PR #124. What I have so far will setup continuous delivery from the slackin Git repo to an Azure Web App (free tier). The limits on the free tier are similar to Heroku -- sleep during a period of inactivity and a maximum compute time.

from slackin.