Yeah - I had a previous post that was successful on HackerNews. Brought the site down, so I took it offline, enabled aggressive & static caching (was previously normal caching), as well as Boost. Imported database to prod, restarted - mostly fixed it, but had to boost my RAM to 1GB, then it survived the rest of the storm. With this happening again, at small 13 points for this post, I'm the same as you - glad to be out of that world.
Since you're into the node world already, check out docpad (https://github.com/bevry/docpad) instead of Jekyll. It doesn't have the same GitHub integration unfortunately, but it can still be hosted in a gh-pages branch.
It supplants Meteor's mongodb/minimongo syncing and its authentication system.
The only thing it lacks is a client layer. But for me that's a feature because in the past 2 years lots of reliable client side stacks have popped up, and both derby and meteor's custom client stack are disgusting.
I've been using Meteor but I'm thinking about abandoning it in favor of firebase/angular.
Edit: can you show us a cached link to your derby vs Meteor comparison please.
KaoruAoiShiho, I'm really liking the look of this Firebase. Are you yourself set on Angular as the client? I feel inclined towards your opinions: a man who comes from Drupal, uses Meteor, with an eye on Angular, obviously knows what he's talking about ;)
I'm not necessarily set on Angular but I've used Backbone professionally for over a year but it's out of the question now. The other one is emberjs which I haven't played much with but all the literature on the internet that I can find supports angular over ember. I've also reviewed the ember docs and they make several decisions that I don't agree with.
I'm open to other client frameworks but if the Firebase+Angular combo works out it seems to me like the best foundation.
reply