Comments (7)
I think this suggestion can lower the entry barrier for a developer starting to work with Appwrite because it will allow them to begin working with databases and files without requiring them to understand the permission mechanism first.
One issue I am not sure about is what the default should be in cases where we donβt have a logged-in user like when integrating from the server, or when the user is just a guest and have no account.
We should also find out what is the best way to reflect this in the documentation and other guides that might require understanding this process.
from appwrite.
I agree documentations is a must, but we also need to make sure that the getting started guide is easy as possible for people just wanting to play around and get to know Appwrite without diving into all the little details straight away.
Yes if we write the documentation with a lot of examples, then it'll definitely be easy for people to get started. Here's what im suggesting.
- The getting started guide needs to happen regardless. That can contain examples and theory behind appwrite. It must explain about the roles and permissions and also mention that the default permissions are for the current user and admin to read and write, but these permissions can be modified as per you use case
from appwrite.
@christyjacob4 100% about the examples, this is something we really lack right now in this permissions tutorial: https://appwrite.io/docs/permissions
I will add it to my checklist β
from appwrite.
Are we going to allow anonymous users to create documents as well ??
In the documentation I feel we can have a getting started section that explains to the users regarding the various permissions. The getting started section will give an overview of appwrite and explain all the nuances specific to appwrite including permissions and rules.
from appwrite.
@christyjacob4 Currently we do allow anonymous users to create documents, but we can always review and see if this is a real use case or can just be customised and implemented using a server integration. This still leaves us with the question of what happens on a server-to-server integration.
I agree documentations is a must, but we also need to make sure that the getting started guide is easy as possible for people just wanting to play around and get to know Appwrite without diving into all the little details straight away.
from appwrite.
Just to keep this thread up-to-date.
We have updated the permissions docs, making them a lot simpler to understand and we have also added some usage examples: https://appwrite.io/docs/permissions
from appwrite.
We have also updated our default values. From the client side, read and write will be given to the current user by default, on the server API it will be empty for both read and write unless set.
from appwrite.
Related Issues (20)
- π Enhancement: Add support for push notification channels (Android/FCM) HOT 1
- π Bug Report: Missing scope throws Uncaught AppwriteException: Invalid redirect
- π Enhancement: Accepts Hashed Passwords in Login/Signup endpoints HOT 2
- π Bug Report: Stats shows only last 25days, end of every day, it hides 26th day. HOT 4
- π Documentation: What's the realtime websocket URL? HOT 1
- AppwriteException: Database not found HOT 4
- π Bug Report: Recreate Same Name Relationship Attribute Only Self-Hosted HOT 5
- π Bug Report: No logs for failed index
- π Documentation: createToken says it will create a user if they do not exist
- π Bug Report: SMS Sending via TextMagic stuck at "processing" status HOT 1
- π Bug Report: Receiving a general error for correct inputs using an email that account was previously deleted for HOT 1
- π Enhancement: Support Vonage Messages API for Messaging HOT 1
- π Bug Report:
- π Bug Report: Cannot renew domain HOT 6
- π Bug Report: querry does not work on Ios but does work on windows and android when using c# HOT 8
- π Bug Report: Expired targets not automatically deleted HOT 2
- RactNative--500 error HOT 1
- π Bug Report: Server Error using GraphQL HOT 1
- π Bug Report: Unable to get current user session on functions using jwt HOT 1
- π Documentation: Support manual deployment HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from appwrite.