Harry Dry
@harrydry
i thought heroku should handle that also.
i was trying to write images to heroku so i think there was massive problems there. but there could be other problems as well. difficult to tell.
i know this is a bit cheeky, but it would be a dream if you could cast your eye over a few of my controller methods (not even sure if you know node / mongo that well)
I'm still learning myself, but feel free to post something. If I don't see something, maybe someone else here will. Also a clue would be in chrome dev tools, Network tab, if you see long running requests... its no bueno. Building Asynchronous software takes intention though...
Maybe you should look into message queues... like RabbitMQ
Heroku has separate "work dynos" right? Maybe that's key, how to move work from your web dynos to your workers dynos?
node js. pug(jade) for templating.
Bundling js with webpack
Seems like it should support 100 concurrent users. There's probably blocking code somewhere... node.js should block as little as possible.
i thought heroku should handle that also.
i was trying to write images to heroku so i think there was massive problems there. but there could be other problems as well. difficult to tell.
i know this is a bit cheeky, but it would be a dream if you could cast your eye over a few of my controller methods (not even sure if you know node / mongo that well)
I'm still learning myself, but feel free to post something. If I don't see something, maybe someone else here will. Also a clue would be in chrome dev tools, Network tab, if you see long running requests... its no bueno. Building Asynchronous software takes intention though...
Maybe you should look into message queues... like RabbitMQ
Heroku has separate "work dynos" right? Maybe that's key, how to move work from your web dynos to your workers dynos?
had it on hobby . then upgraded to 2X professional. Surely that must cover 100 people at once?
What language/framework are you using?
node js. pug(jade) for templating.
Bundling js with webpack
Seems like it should support 100 concurrent users. There's probably blocking code somewhere... node.js should block as little as possible.
i thought heroku should handle that also.
i was trying to write images to heroku so i think there was massive problems there. but there could be other problems as well. difficult to tell.
i know this is a bit cheeky, but it would be a dream if you could cast your eye over a few of my controller methods (not even sure if you know node / mongo that well)
I'm still learning myself, but feel free to post something. If I don't see something, maybe someone else here will. Also a clue would be in chrome dev tools, Network tab, if you see long running requests... its no bueno. Building Asynchronous software takes intention though...
Maybe you should look into message queues... like RabbitMQ
Heroku has separate "work dynos" right? Maybe that's key, how to move work from your web dynos to your workers dynos?
hey max, this sounds cool. thanks so much. got a few questions though:
a) so if my bundle.js is found here: hd001.herokuapp.com/dist/bund…
would my asset path be hd001.herokuapp.com/dist/ ?
but then i have some images uploaded by users here:
hd001.herokuapp.com/uploads/0… ?
So cant really work out my asset path
A couple of years ago the media were calling for Roger Federer to retire. He was on an bad run of and slipping down the rankings. When asked in an interview about retiring he said this:
"Sometimes you're just happy playing. Some people, some media, unfortunately, don't understand that it's okay just to play tennis and enjoy it. They always think you have to win everything, it always needs to be a success story, and if it's not, obviously, what is the point? Maybe you have to go back and think, Why have I started playing tennis? Because I just like it. It's actually sort of a dream hobby that became somewhat of a job. Some people just don't get that, ever."
This summarises me my mindset. Replace the words "play tennis" with "make stuff" and reread Federer's answer.
yep