Ok, the conversion is done, hubski.com publications are now stored in SQL.
It was a big change: there are bugs. If you see a bug, make a post tagged #bugski and mention me, rob05c.
The title is a bit misleading, it isn't all our data. Publications are the vast majority, but other things like user data are still in flat files. I'll be converting those to SQL in the near future. I'll also be adapting the internal API to not serve private data, and serving it externally in the near future. It's only publications, so it's a long way from a complete API that you could use to e.g. make a mobile app. But it gives the devs out there something to play with, if you like.
I'll also be bringing hubski.com down and back up a couple times this weekend, probably late at night, to verify loading and saving to SQL works properly. Restarting the app takes about 30 minutes.
As always, let me know if you have any questions.
Woooooooooooooooooooo. Yay! I'm glad we are back
Hey rob05c: any recommendations on where to start with learning SQL? I work with a lot of machine data which is stored in SQL and then generally formatted into many different reports, and have recently been pulling directly from the SQL server and could see a lot of value in learning how that actually works.
That's a feature mk did right before the conversion. I think I like it better for someone else's page, but prefer shares first on my own page. I use my use page as a landing, to quickly see if there are new comments on things I shared. And I don't really care about my own comments. Meh.