
I find relatonships are so basic and support many less features than Appwrite's competitors. I can't create relationship with files I can't see buckets in the collections list as well as users.
How can we build a relationship system between files and also users. This is blocking me from going with the appwrite.
I tried supabase self-hosted but jesus, that's not okay for selfhosting. Thankfully appwrite has great self hosting support.
Please help this guy

There's no built in support for creating relationships among Storage Files x User. What you could do is either use Permissions on Storage buckets, use User Prefs or create a dedicated collection for user with permissions so that only they can access them. You haven't described your usecase so this is just a very basic approach.

It will be like a product catalog. I want to assign files to each product document including pdfs, sheets and docx files. and same for images png and jpg. those files will be publicly assessible

I see.. Here's something I've done recently.
Make storage buckets, keep note of their ID
s.
Use those ID
s in your collection for reference.
Example Bucket -
PS5 Consoles (id: ps5_consoles
)
Example Collection Attribute -
bucketId
- ps5_consoles
.
Then you can list the contents of the bucket as usual.

yes that is useful thanks

If your query is resolved, please mark the thread as [SOLVED]. If you have additional queries, make sure to create a new thread.
Happy Appwriting :appwritecheers:.
Recommended threads
- Relationships restricted to a max depth ...
When I do query like: ``` await _databases.listDocuments( databaseId: AppwriteConfig.DATABASE_ID, collectionId: AppwriteConfig.SERVICES_COLLECTI...
- How can we add more than 8 attributes in...
Hey, when I tried to add attribute in my collection it showed me this Error "The maximum number or size of attributes for this collection has been reached." How...
- Invalid credentials after migration
Hi everyone! After migrating our self-hosted Appwrite 1.3.1 to another server (staging, so a different domain), we are now getting 'Invalid credentials' when ...
