Hacker News Reader

Comment by lukeholder | Hacker News Reader

Wow, congrats. Great work.

Anyone know if they are close to having proper auth in the client for DB work yet?

While it hasn't landed in the master branch yet, you can follow the progress of auth support in the auth branch: https://github.com/meteor/meteor/tree/auth

Thanks for sharing this!

Thanks.

Yes, we now have an authentication system that lets you define limits on which documents each client can read and modify. It's available on the "auth" branch in the Meteor repository.

https://github.com/meteor/meteor/wiki/Getting-Started-with-A...

Do you have an ETA when you will officially release Meteor with auth?

this.

i can't even touch it until i know i can make sure a client can't even see the existence of rows it's not allowed to read.

That's precisely how Meteor auth works. Each client can request a set of documents from the server -- think of it as a predefined query. For each of those requests, your server code decides what (if anything) to send back to the client.

That's exactly what I was going to ask. That's the one thing keeping me from building something serious with Meteor.

The rest I tried, and it does look really nice for real-time webapps, as soon as the Javascript development environment grows up a bit more.

Reply on news.ycombinator.com