2 ms·
In the future, you should avoid committing your Parse application id and client key publicly... You don't want other dev's piggybacking on your account quota, t
by gfosco 13y ago
In the future, you should avoid committing your Parse application id and client key publicly... You don't want other dev's piggybacking on your account quota, though it's not really a security risk by itself. Considering it's already there, make sure you've implemented Class-level security to protect your data. https://www.parse.com/docs/data#security-classes https://www.parse.com/docs/data#security-classes
- embwbam 13y agoYou're only looking at the dev key. I have a separate "secret" branch with the production keys for everything. It hits a different firebase too.