Hosting for Socket.io is a pain
thebyrd opened this issue · 5 comments
Heroku only allows long polling and has memory limits so it'll only last a couple hours before you exceed the memory limit and it shuts down.
I also have a feeling that the way I put the socket.io code in a controller may be part of the problem. @sjkaliski, can you take a look at this? Thx.
I'm going to switch this over to slanger.
#startuplife
—
Sent from phone
On Sat, Mar 9, 2013 at 6:50 PM, David Byrd notifications@github.com
wrote:
I'm going to switch this over to slanger.
Reply to this email directly or view it on GitHub:
#2 (comment)
AWS or die.
—
Sent from Mailbox for iPhone
On Sat, Mar 9, 2013 at 6:03 PM, Vivek Patel notifications@github.com
wrote:
#startuplife
—
Sent from phone
On Sat, Mar 9, 2013 at 6:50 PM, David Byrd notifications@github.com
wrote:I'm going to switch this over to slanger.
Reply to this email directly or view it on GitHub:
#2 (comment)
Reply to this email directly or view it on GitHub:
#2 (comment)
@sjkaliski I think its more an issue of me not understanding how Socket.io works. Your last commit didn't fix the memory issues.
Fuck. Well I'll take a more in depth look later. Was tryna bust it out in a rush.
—
Sent from Mailbox for iPhone
On Sat, Mar 9, 2013 at 6:44 PM, David Byrd notifications@github.com
wrote:
@sjkaliski I think its more an issue of me not understanding how Socket.io works. Your last commit didn't fix the memory issues.
Reply to this email directly or view it on GitHub:
#2 (comment)