4 ms·
>* Use Meteor.publish() and Meteor.subscribe() to control what clients can see (remove the 'autopublish' package first). Actually you may not need to do this fo
by heretohelp 15y ago
>* Use Meteor.publish() and Meteor.subscribe() to control what clients can see (remove the 'autopublish' package first). Actually you may not need to do this for a blog.
Scoping isn't enough.
>* Use Meteor.methods() and Meteor.call() to define secure server functions and call them from the client. Then lock down your app by disabling the "training wheel" methods that let any client do any write."
So, I can't make a production-grade app unless I use 0% of the magic.
- foolinator 15y agoYou're absolutely right. But all frameworks have to go through these humps. Hell, I remember just 2 years ago having MongoDB in production it would regularly crash. We got rid of it in production, but I'd reconsider using it now.
- StavrosK 15y agoWhich features, are making you consider MongoDB? I'm asking because I wrote a (really short and small) MongoDB-ish abstraction layer over SQLite the other day (https://github.com/stochastic-technologies/goatfish https://github.com/stochastic-technologies/goatfish), and it seems to me that it's trivial to emulate the MongoDB queries and various other features over SQL without all the hassle of it eating your data or requiring 100 GB of RAM for a few indices.