Hi everyone,
My apologies, I didn't expect to end up Top of HN. I'll try and get it back up.
In the meantime, here is the YouTube video: http://www.youtube.com/watch?v=cxf8f9AQBgM&feature=plcp
My apologies, I didn't expect to end up Top of HN. I'll try and get it back up.
In the meantime, here is the YouTube video: http://www.youtube.com/watch?v=cxf8f9AQBgM&feature=plcp
I'm also curious if there's an easy code import/export feature for individual widgets and/or the entire dashboard (all widgets, global styling, settings, etc). I don't think I'd use it for anything serious without being able to export the entire dashboard page and add it to my git repo (and being able to reload it if somethings gets lost or messed up). And being able to import/export individual widgets would make it easy for the community to share custom widgets so that in practice end users wouldn't actually have to write much code.
Anyway, it looks like a cool project!
EDIT: I see now there are REST api endpoints for creating & getting a dashboard, awesome.
Once again, my apologies for the downtime.
For some reason, this was the case:
$ ulimit -n
> 1024
The site is alive, but may still be intermittent. Will keep you updated.
but.
In general terms - what does a potential user of this service conclude if the server appears to be hosted on a single machine and the admin staff doesn't seem to know how ulimit works?
(Yes, I realize this is ycombinator and about ideas and VC and all that.... just throwing the concept out there.)
Great product, but total lack of either understanding or preparedness on the lower levels.
It was unfortunate that this ulimit issue occurred and I apologise for that.
I knew about ulimit from 2 sources (a LinkedIn article on Node.js practices) and a 2nd source from a hosting service's documentation.
The fault (and it was mine) was that I didn't realise that in order to persist the ulimit setting between reboots, you had to set it in a configuration file.
Originally, the application was hosted across multiple instances and proxied, but due to the nature of the WebSocket library and it's use of transports with the proxy library, the connection was intermittent, so I reverted to a single instance. Since resolving the ulimit issue, this application has stayed up.
As for admin staff, you may be surprised to learn there is no company with multiple devs, designers, product people and sysadmin behind all this. This is all my work, all 2 and a bit months of it.
Fantastic site, by the way.
I mean, it's neat (understatement of the week) and all; but where do you plan on going from here?
Thanks. At this point, I need to go and find some work as my bank balance doesn't look great.
I'm going to continue working on it in some capacity, and I will investigate turning it into a SaaS.
There are some components of the app which would be worth open-sourcing, in order to assist others with building SocketStream applications.
Thanks again.
Good luck with your other gigs as well.