We're a group of makers shipping together. We help each other stay accountable and reach our goals.
Apply for access
Quang Van
@lessfocus
Front-page loads quick!
I think the charts could be more baller (visually attractive)
As for the idea, I like the dashboard concept... public dashboard could be interesting... I personally am too paranoid for public dashboard I think.
Also there seems to be a trust factor that's needed, assuming there's an API of yours we'd have to ping every time something happens. Which is an intimate integration.
Perhaps something like public web/traffic/shared stats would be less intimate/invasive and easier/less-friction to integrate.
But overall great job for 3 weeks of work!
Though Vue has tempted me, my current front-end framework in use is still React.
is there something online you built with react? :)
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?
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?
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?
I'm having this same problem...
kenw on the foundercafe forum said this to me:
Regardless of tech stack, this matters more:
1.are you solving a problem
2.for a customer who understands they have a problem, and
3.that customer is willing to pay someone to solve that problem, and
4.those customers are willing to pay you to solve that problem, and
5.there are enough of those customers willing to buy your solution, and
6.you have a way to find and market to them in a repeatable fashion
7.you enjoy the customers and helping them find a solution to their problem
8.you enjoy maintaining and improving the solution you have built.
If you can say yes to those things, who cares what the stack is, you’re gonna have good times.
Maybe key is to know what's important and what's not... just keep moving forward.
not sure, but I bet it'll be popular